Skip to main content
CVE-2025-11074VulnerabilityPublished Updated

CVE-2025-11074: code-projects Project Monitoring System · SQL Injection

Affects code-projects Project Monitoring SystemSource CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Sep 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 Project Monitoring SystemAffected
  • =1.0
Fixed in–

AI-suggested

Since no official patches are currently available, European organizations should take immediate steps to mitigate risk. First, implement web application firewalls (WAFs) with rules specifically designed to detect and block SQL injection attempts targeting the /login.php endpoint and parameters 'username' and 'password'. Conduct thorough input validation and sanitization on all user-supplied data, employing parameterized queries or prepared statements to prevent injection. Restrict database user privileges to the minimum necessary to limit the impact of potential exploitation. Monitor logs for unusual login activity or database errors indicative of injection attempts. Consider temporarily disabling or restricting external access to the affected Project Monitoring System until a patch or update is released. Engage with the vendor or community to obtain or develop patches. Additionally, perform regular security assessments and penetration testing focused on injection vulnerabilities. Educate developers and administrators on secure coding practices to prevent similar issues in future versions.

Description

A flaw has been found in code-projects Project Monitoring System 1.0. The impacted element is an unknown function of the file /login.php. This manipulation of the argument username/password causes sql injection. The attack may be initiated remotely. The exploit has been published and may be used.

References

Community reviews

Loading reviews…