Skip to main content
CVE-2025-13579VulnerabilityPublished Updated

CVE-2025-13579: code-projects Library System · SQL Injection

Affects code-projects Library SystemSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
code-projects Library SystemAffected
  • =1.0
Fixed in–

AI-suggested

To mitigate this vulnerability, organizations should immediately implement input validation and sanitization on the 'ID' parameter in /return.php. The best practice is to refactor the code to use parameterized (prepared) SQL statements or stored procedures to prevent injection. If patching is not yet available, deploying a Web Application Firewall (WAF) with rules to detect and block SQL injection patterns targeting the vulnerable parameter can reduce risk. Monitoring database logs for unusual queries or access patterns is recommended to detect exploitation attempts early. Restricting database user permissions to the minimum necessary can limit the impact of a successful injection. Additionally, organizations should plan to upgrade to a patched version once released and conduct security testing on all web inputs. Educating developers on secure coding practices to prevent similar vulnerabilities in future releases is also advised.

Description

A vulnerability was found in code-projects Library System 1.0. This impacts an unknown function of the file /return.php. The manipulation of the argument ID results in sql injection. The attack can be launched remotely. The exploit has been made public and could be used.

References

Community reviews

Loading reviews…