Skip to main content
CVE-2025-13575VulnerabilityPublished

CVE-2025-13575: code-projects Blog Site · SQL Injection

Affects code-projects Blog SiteSource 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 24% 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 Blog SiteAffected
  • =1.0
Fixed in–

AI-suggested

1. Immediately review and restrict database user permissions to the minimum necessary, preventing excessive privileges that could be exploited via SQL injection. 2. Implement input validation and sanitization on all user-supplied data, especially the parameters handled by the category_exists function. 3. Refactor the vulnerable code to use parameterized queries or prepared statements to eliminate direct concatenation of user inputs into SQL commands. 4. Monitor web application logs and network traffic for unusual SQL query patterns or repeated requests targeting the vulnerable endpoints. 5. If a patch becomes available from the vendor, prioritize its deployment after testing. 6. Employ Web Application Firewalls (WAFs) with rules designed to detect and block SQL injection attempts targeting the affected endpoints. 7. Conduct security audits and penetration testing focused on injection vulnerabilities in the blog platform. 8. Educate developers and administrators on secure coding practices and the risks of SQL injection to prevent similar issues in future releases.

Description

A security vulnerability has been detected in code-projects Blog Site 1.0. Impacted is the function category_exists of the file /resources/functions/blog.php of the component Category Handler. Such manipulation of the argument name/field leads to sql injection. The attack may be performed from remote. The exploit has been disclosed publicly and may be used. Multiple endpoints are affected.

References

Community reviews

Loading reviews…