CVE-2025-13576: code-projects Blog Site · Improper Authorization
Affects code-projects Blog SiteSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 26 Oct 2026, 09:15 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 23% 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:PExploitation evidence
Disclosed: evidence found.
CVE published 24 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| code-projects Blog Site | Affected
| Fixed in– |
AI-suggested
1. Immediately restrict access to the /admin.php endpoint using network-level controls such as IP whitelisting or VPN-only access to limit exposure. 2. Deploy and configure a Web Application Firewall (WAF) to detect and block unauthorized requests targeting the admin interface. 3. Conduct a thorough code review of the authorization logic in /admin.php and related endpoints to identify and remediate access control flaws. 4. Monitor web server logs and application logs for unusual or unauthorized access attempts to administrative functions. 5. Implement multi-factor authentication (MFA) for all administrative access to add an additional security layer. 6. Engage with the vendor or community to obtain or develop patches and apply them promptly once available. 7. Educate administrators and developers about secure coding practices, especially regarding authorization checks. 8. Consider isolating the blogging platform in a segmented network zone to limit lateral movement if compromised. 9. Regularly update and patch all related software components to reduce the attack surface. 10. Prepare an incident response plan specific to web application compromises to enable rapid containment and recovery.
Description
A vulnerability was detected in code-projects Blog Site 1.0. The affected element is an unknown function of the file /admin.php. Performing manipulation results in improper authorization. It is possible to initiate the attack remotely. The exploit is now public and may be used. Multiple endpoints are affected.