CVE-2025-11104
BaseFortify
Publication date: 2025-09-28
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 | electricity_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-11104 is a critical SQL injection vulnerability in CodeAstro Electricity Billing System version 1.0, specifically in the /admin/bill.php file. The vulnerability occurs because the 'uid' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This flaw enables remote attackers to manipulate SQL queries without authentication, potentially compromising the system's confidentiality, integrity, and availability. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, allowing attackers to leak sensitive data, tamper with or delete data, gain full control over the system, and disrupt services. It severely compromises system security and business continuity by enabling attackers to manipulate SQL queries remotely without authentication. [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 'uid' parameter in the /admin/bill.php endpoint for SQL injection. You can use SQL injection testing tools such as sqlmap to automate detection. Example sqlmap command: sqlmap -u "http://target/ebill/admin/bill.php?uid=1" --risk=3 --level=5 --batch. Additionally, manual testing can be done using payloads like 'uid=1 AND 3954=3954' (Boolean-based), 'uid=1 AND (SELECT 3545 FROM(SELECT COUNT(*),CONCAT(...))a)' (Error-based), 'uid=1 AND (SELECT 6921 FROM (SELECT(SLEEP(5)))lYRX)' (Time-based), or UNION-based injections such as 'uid=-2573 UNION ALL SELECT NULL,CONCAT(...)'. Google dorking can also help identify vulnerable targets using the query: inurl:admin/bill.php. [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) Enforce strict input validation and filtering to ensure inputs conform to expected formats. 3) Minimize database user permissions by avoiding use of high-privilege accounts for routine operations. 4) Conduct regular security audits to detect and address vulnerabilities promptly. If possible, replace or update the affected component or product to a version without this vulnerability. [2, 3, 1]