Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Input neutralization, injection prevention
|
| Impact | The CVSS 3.1 score of 7.3 reflects a high-severity vulnerability with network-accessible attack vector (AV:N), low attack complexity (AC:L), and no privilege requirement (PR:N), indicating ease of exploitation. The vector also indicates confidentiality, integrity, and availability impact (C:L/I:L/A:L), though not complete compromise. The public availability of a proof-of-concept exploit significantly elevates real-world risk. Without EPSS data or KEV confirmation provided, the disclosure status indicates active threat potential. The vulnerability qualifies as high-priority because: (1) attack surface is unauthenticated remote access, (2) SQL injection allows database exfiltration and potential code execution via stacked queries or INTO OUTFILE, (3) POC exists enabling rapid weaponization, and (4) small-scale billing systems often lack security monitoring. This is NOT a false-high-CVSS issue—it represents genuine, immediately exploitable risk. |
| Exploit ScenarioDerived | An attacker sends a POST request to http://target/user/change_password.php with payload: new_password=password' UNION SELECT user(),version(),database() -- . This breaks out of the intended UPDATE or INSERT statement, allowing the attacker to extract database metadata, enumerate table names (information_schema), and dump sensitive data (customer names, addresses, payment records, account balances). Advanced exploits could use stacked queries (;DROP TABLE users; --) to destroy data or enable reverse shells via INTO OUTFILE on writable directories. Since authentication is not required (PR:N), any internet-connected attacker can perform reconnaissance and exploitation without prior system access. POC code is publicly available, reducing the barrier to entry for script-kiddies and organized attackers. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAI
CVE-2025-7610 is a critical SQL injection vulnerability in code-projects Electricity Billing System 1.0 affecting the password change functionality at /user/change_password.php. An unauthenticated remote attacker can inject arbitrary SQL commands through the new_password parameter to read, modify, or delete database contents. The vulnerability has been publicly disclosed with proof-of-concept code available, making active exploitation highly probable.
RemediationAI
Immediate actions: (1) Apply input validation to reject SQL metacharacters in password fields or implement strict allowlists (alphanumeric + symbols only), (2) Use parameterized queries/prepared statements with bound parameters in the password update query, (3) Implement WAF rules to detect and block SQL injection payloads in the new_password parameter. Long-term: Update to a patched version when released by code-projects (monitor their GitHub or advisory channels for v1.1+). Workaround: Temporarily disable the /user/change_password.php endpoint or restrict access via IP whitelisting/authentication middleware until patching is feasible. Database-level: Implement principle-of-least-privilege on the database user account used by the application (remove DROP, ALTER, FILE privileges).
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
This vulnerability is a classic SQL injection flaw (CWE-74: Improper Neutralization of Special Elements used in an SQL Command) in a PHP-based web application. The root cause is insufficient input validation and parameterized query usage in the password change function. The new_password parameter is concatenated directly into SQL queries without proper escaping or prepared statement usage. The affected application is code-projects Electricity Billing System, a PHP-based billing management solution commonly deployed in small-to-medium enterprises. The vulnerable file /user/change_password.php processes user input without sanitization, allowing attackers to break out of the intended SQL context and execute arbitrary commands against the backend database (typically MySQL/MariaDB).
Know when Electricity Billing System gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
4DescriptionCVE.org
A vulnerability was found in code-projects Electricity Billing System 1.0 and classified as critical. Affected by this issue is some unknown functionality of the file /user/change_password.php. The manipulation of the argument new_password leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.
Executive ViewAI
A critical SQL injection vulnerability in the Electricity Billing System password change function allows unauthenticated remote attackers to compromise user accounts and extract sensitive billing data. With public exploit code available and no patch released, this poses an immediate risk to customer data, billing integrity, and regulatory compliance across all systems using this software.
Deploy Web Application Firewall rules to block SQL injection payloads in password parameters; restrict access to /user/change_password.php via network segmentation or IP whitelisting; disable the password change feature if not critical and force password resets through alternative secure channels; implement database query monitoring and rate limiting; require multi-factor authentication for password changes; apply principle of least privilege to database user accounts.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
EUVD-2025-21353
NVD
CVE.org
EPSS
GitHub
VulDB
Exploit-DB