CVE-2025-10780
BaseFortify
Publication date: 2025-09-22
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| codeastro | simple_pharmacy_management_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-10780 is a critical SQL injection vulnerability in CodeAstro Simple Pharmacy Management version 1.0, specifically in the /view.php file. The vulnerability occurs because the 'bar_code' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This can lead to unauthorized access to the database, enabling attackers to view, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can result in unauthorized database access, data leakage, modification, or deletion of sensitive information. Attackers may also disrupt services or potentially gain full system compromise. This threatens the confidentiality, integrity, and availability of the affected system and its data. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'bar_code' parameter in the /view.php file for SQL injection. A proof-of-concept payload uses a time-based blind SQL injection with the MySQL SLEEP function, for example: `bar_code=1' AND (SELECT 4381 FROM (SELECT(SLEEP(5)))WxZO) AND 'vdOU'='vdOU`. You can test this manually by sending crafted POST requests with this payload or use automated tools like sqlmap to detect and confirm the SQL injection vulnerability. Additionally, attackers may be identified by monitoring for unusual or suspicious requests targeting /view.php with SQL injection patterns. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Apply strict input validation and filtering on the 'bar_code' parameter to ensure it conforms to expected formats. 3) Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts such as 'root' or 'admin' for routine operations. 4) Conduct regular security audits of code and systems to detect and fix vulnerabilities promptly. If possible, consider replacing the affected product with a secure alternative. [2, 3, 1]