Skip to main content
CVE-2025-11552VulnerabilityPublished

CVE-2025-11552: code-projects Online Complaint Site · SQL Injection

Affects code-projects Online Complaint 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 31% 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 9 Oct 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 Online Complaint SiteAffected
  • =1.0
Fixed in–

AI-suggested

1. Immediately audit and review the /admin/category.php code to identify and remediate unsafe handling of the 'Category' parameter. 2. Implement parameterized queries or prepared statements to prevent SQL injection attacks. 3. Restrict access to the administrative interface using network segmentation, VPNs, or IP whitelisting to limit exposure. 4. Monitor web server and database logs for unusual query patterns or repeated failed attempts targeting the 'Category' parameter. 5. If possible, apply vendor patches or updates; if none are available, consider temporary workarounds such as input validation filters or web application firewalls (WAFs) configured to block SQL injection payloads. 6. Conduct security testing, including automated scanning and manual penetration testing, to verify the vulnerability is fully mitigated. 7. Educate developers and administrators on secure coding practices and the importance of input validation. 8. Maintain an incident response plan to quickly address any exploitation attempts. These steps go beyond generic advice by focusing on code-level fixes, access controls, and proactive monitoring specific to this vulnerability and product.

Description

A vulnerability was identified in code-projects Online Complaint Site 1.0. This impacts an unknown function of the file /admin/category.php. Such manipulation of the argument Category leads to sql injection. It is possible to launch the attack remotely. The exploit is publicly available and might be used.

References

Community reviews

Loading reviews…