Skip to main content
CVE-2025-11611VulnerabilityPublished Updated

CVE-2025-11611: SourceCodester Simple Inventory System · SQL Injection

Affects SourceCodester Simple Inventory 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 11 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
SourceCodester Simple Inventory SystemAffected
  • =1.0
Fixed in–

AI-suggested

European organizations using SourceCodester Simple Inventory System 1.0 should immediately implement the following mitigations: 1) Apply any official patches or updates from the vendor as soon as they become available. 2) If patches are unavailable, implement input validation and sanitization on the 'uemail' parameter to block malicious SQL syntax. 3) Refactor the application code to use parameterized queries or prepared statements to prevent SQL injection. 4) Restrict database user privileges to the minimum necessary, avoiding use of high-privilege accounts for application connections. 5) Employ Web Application Firewalls (WAFs) with SQL injection detection rules to block exploit attempts. 6) Conduct security audits and penetration testing focused on injection flaws. 7) Monitor logs for suspicious database query patterns or repeated access attempts to /user.php. 8) Educate development teams on secure coding practices to prevent similar vulnerabilities. These steps go beyond generic advice by focusing on immediate code-level fixes, privilege restrictions, and proactive detection tailored to this specific vulnerability.

Description

A weakness has been identified in SourceCodester Simple Inventory System 1.0. Impacted is an unknown function of the file /user.php. This manipulation of the argument uemail causes sql injection. The attack is possible to be carried out remotely. The exploit has been made available to the public and could be exploited.

References

Community reviews

Loading reviews…