CVE-2025-8503

7.3

code-projects · Online Medicine Guide

A SQL injection vulnerability in the Online Medicine Guide 1.0 allows remote, unauthenticated attackers to execute arbitrary database queries via the mname parameter in adaddmed.php.

Executive summary

A critical SQL injection vulnerability in code-projects Online Medicine Guide 1.0 allows for unauthenticated remote exploitation, posing a significant risk of database compromise.

Vulnerability

This vulnerability is a SQL injection flaw (CWE-89) triggered by improper sanitization of the mname argument within the adaddmed.php file. The vulnerability is remotely exploitable by an unauthenticated attacker, allowing them to manipulate backend database interactions.

Business impact

Successful exploitation of this flaw could allow unauthorized actors to read, modify, or delete sensitive data stored within the application database. Given the CVSS score of 7.3, this represents a significant risk to data confidentiality and integrity, potentially leading to unauthorized access to patient or medical information managed by the platform.

Remediation

Immediate Action: As no official vendor patch is currently available, administrators should restrict network access to the application or disable the vulnerable adaddmed.php component until a secure update is provided.

Proactive Monitoring: Review web server access logs for anomalous requests containing SQL syntax patterns or unexpected input in the mname parameter.

Compensating Controls: Implement a Web Application Firewall (WAF) with rules configured to detect and block common SQL injection payloads targeting input parameters.

Exploitation status

Public Exploit Available: Yes, a published proof-of-concept exists as documented in the GitHub issue referenced by the vulnerability record.

Analyst recommendation

The presence of a public proof-of-concept combined with the unauthenticated nature of this vulnerability necessitates immediate defensive action. Organizations using code-projects Online Medicine Guide 1.0 must prioritize isolating the affected component and deploying compensating controls to mitigate the risk of unauthorized database access while awaiting a vendor-supplied security update.

More code-projects CVEs

Sources

Originally found and disclosed by Haoatao (VulDB User), per the CVE Program record.