CVE-2025-8924
BaseFortify
Publication date: 2025-08-13
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 | online_water_billing_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-8924 is a critical SQL injection vulnerability in Campcodes Online Water Billing System version 1.0, specifically in the /viewbill.php file. The vulnerability arises from improper validation and sanitization of the 'id' parameter, allowing attackers to inject malicious SQL code into database queries. This enables unauthorized access to the database, allowing attackers to retrieve, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, data tampering, full system compromise, and service disruption. Attackers can exploit it remotely without authentication to retrieve, modify, or delete sensitive information, potentially causing loss of confidentiality, integrity, and availability of the system. [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 /viewbill.php?id= parameter for SQL injection using tools like sqlmap. For example, you can run: sqlmap -u "http://<target>/Water_Billing_System/viewbill.php?id=16" --batch to check for SQL injection. Additionally, manual testing with payloads such as 'id=-8575' OR 2266=2266 #' (Boolean-based), error-based, time-based (e.g., id=16' AND SLEEP(5)), or UNION-based injection payloads can help identify the flaw. Also, Google dorking with "inurl:viewbill.php" can help identify vulnerable targets. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, applying strict input validation and filtering on the 'id' parameter, minimizing database user permissions by avoiding high-privilege accounts for the application database connection, and conducting regular security audits. Since no known countermeasures are documented, replacing the affected software with an alternative product is also suggested. [2, 3]