CVE-2025-9811
BaseFortify
Publication date: 2025-09-02
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-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-9811 is a SQL injection vulnerability in Campcodes Farm Management System version 1.0, specifically in the /reviewInput.php file. The vulnerability occurs because the "rating" parameter is used directly in SQL queries without proper sanitization or validation, allowing attackers to inject malicious SQL code remotely without authentication. This enables unauthorized manipulation of the database queries. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, data tampering, full system control, and potential service disruption. Attackers can execute arbitrary SQL commands remotely, compromising the confidentiality, integrity, and availability of the system. Exploitation does not require user authentication, increasing the risk. [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 /reviewInput.php endpoint for SQL injection in the 'rating' parameter. A proof-of-concept exploit involves sending a crafted POST request to /AgroCulture/reviewInput.php?pid=1 with a payload such as: rating=' AND updatexml(1,concat(0x7e,(select database()),0x7e),1) AND 'a'='a. Additionally, attackers may be identified by searching for the vulnerable URL pattern using Google dorking with queries like "inurl:reviewInput.php". Network detection could involve monitoring for suspicious POST requests containing SQL injection payloads targeting the 'rating' parameter. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input; 2) Applying strict input validation and filtering on the 'rating' parameter to ensure it conforms to expected formats; 3) Minimizing database user permissions by avoiding use of high-privilege accounts for routine database operations; 4) Conducting regular security audits of code and systems to detect and remediate vulnerabilities promptly. If possible, consider replacing the affected software with an alternative product. [2, 3]