Unauthenticated SQL injection via unsanitized ID parameter
Published Jul 8, 2025 · Updated Jul 8, 2025
SQL injection in code-projects Library System 1.0 allows remote attackers to access and alter database data through approve.php. The approve.php handler passes the GET id parameter directly into SQL queries without validation, sanitization, or parameter binding. No login or authorization is required; crafted values support boolean-, error-, and time-based injection that reads or changes database data.
Summary
What happened
SQL injection in code-projects Library System 1.0 allows remote attackers to access and alter database data through approve.php. The approve.php handler passes the GET id parameter directly into SQL queries without validation, sanitization, or parameter binding. No login or authorization is required; crafted values support boolean-, error-, and time-based injection that reads or changes database data.
The record
- CVE
- CVE-2025-7185
- Published
- Jul 8, 2025
- Updated
- Jul 8, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-89, CWE-74, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 8, 2025CVE publishedPublication date reported by the CVE source.
- Jul 8, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- HeDunSec approve.php SQL injection proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo