Database disclosure via concatenated return identifier
Published Nov 24, 2025 · Updated Feb 24, 2026
SQL injection in return.php in code-projects Library System 1.0 allows remote attackers to read database contents through the id parameter. The handler directly concatenates the GET value into an SQL query without validation or parameter binding. The proof of concept reports no login gate and demonstrates boolean-, error-, and time-based injection, although CNA metrics encode low privileges.
Summary
What happened
SQL injection in return.php in code-projects Library System 1.0 allows remote attackers to read database contents through the id parameter. The handler directly concatenates the GET value into an SQL query without validation or parameter binding. The proof of concept reports no login gate and demonstrates boolean-, error-, and time-based injection, although CNA metrics encode low privileges.
The record
- CVE
- CVE-2025-13579
- Published
- Nov 24, 2025
- Updated
- Feb 24, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-74, CWE-89, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 24, 2025CVE publishedPublication date reported by the CVE source.
- Feb 24, 2026Record 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
- return.php id parameter 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