Skip to main content
CVE-2025-11610VulnerabilityPublished Updated

CVE-2025-11610: 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

1. Immediately audit all instances of SourceCodester Simple Inventory System version 1.0 and identify affected deployments. 2. Implement input validation and sanitization on the editBrandName parameter to prevent SQL injection, preferably by using parameterized queries or prepared statements in the codebase. 3. Employ Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting /brand.php and related endpoints. 4. Monitor database logs and application logs for unusual query patterns or failed injection attempts. 5. Restrict database user privileges to the minimum necessary to limit the impact of potential injection attacks. 6. Isolate the inventory system from critical network segments to reduce lateral movement risk. 7. Engage with the vendor or community to obtain or develop patches or updated versions addressing this vulnerability. 8. Conduct security awareness training for developers and administrators on secure coding practices and vulnerability management. 9. Plan for incident response readiness in case exploitation is detected. 10. Consider alternative inventory management solutions if timely patching is not feasible.

Description

A security flaw has been discovered in SourceCodester Simple Inventory System 1.0. This issue affects some unknown processing of the file /brand.php. The manipulation of the argument editBrandName results in sql injection. The attack can be executed remotely. The exploit has been released to the public and may be exploited.

References

Community reviews

Loading reviews…