CVE-2025-9726
BaseFortify
Publication date: 2025-08-31
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 |
|---|---|---|
| campcodes | farm_management_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-9726 is a critical SQL injection vulnerability in Campcodes Farm Management System version 1.0, specifically in the /review.php file. The vulnerability occurs because the application improperly handles the 'pid' parameter, allowing attackers to inject malicious SQL code due to insufficient input sanitization. This flaw enables remote, unauthenticated attackers to execute arbitrary SQL commands, potentially compromising the confidentiality, integrity, and availability of the system. [1, 2]
How can this vulnerability impact me? :
Exploiting this vulnerability can lead to unauthorized database access, data leakage, data tampering, full system control, and potential service disruption. Since no authentication is required, attackers can remotely exploit the flaw to compromise system security and disrupt business continuity. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking for the presence of the vulnerable /review.php file and testing the 'pid' parameter for SQL injection. One method is to use crafted HTTP GET requests to the endpoint, for example: curl "http://<target>/review.php?pid=1' and updatexml(1,concat(0x7e,(select database())),1)#" to see if the response indicates SQL injection. Additionally, Google dorking with queries like "inurl:review.php" can help identify potentially vulnerable targets. Monitoring network traffic for suspicious requests targeting /review.php with unusual 'pid' parameter values can also help detect exploitation attempts. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Apply strict input validation and filtering on the 'pid' 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 the code and system to identify and fix vulnerabilities. If possible, replace the affected product with an alternative solution as no official patches are documented. [1, 2]