Skip to main content
CVE-2025-11431VulnerabilityPublished

CVE-2025-11431: code-projects Web-Based Inventory and POS System · SQL Injection

Affects code-projects Web-Based Inventory and POS 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 33% 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 8 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 Web-Based Inventory and POS SystemAffected
  • =1.0
Fixed in–

AI-suggested

Organizations should immediately audit their use of the code-projects Web-Based Inventory and POS System version 1.0 and identify any instances of the vulnerable /transaction.php endpoint. Specific mitigations include: 1) Implementing parameterized queries or prepared statements to eliminate SQL injection vectors in the 'shopid' parameter; 2) Applying rigorous input validation and sanitization to ensure only expected data types and values are accepted; 3) Employing Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting this parameter; 4) Monitoring logs for suspicious query patterns or repeated access to /transaction.php with anomalous 'shopid' values; 5) Restricting network access to the POS system to trusted IPs where feasible; 6) Engaging with the vendor or community to obtain or develop patches or updates addressing this vulnerability; 7) Conducting penetration testing to verify the effectiveness of mitigations. These steps go beyond generic advice by focusing on the specific vulnerable parameter and the operational context of the POS system.

Description

A vulnerability was determined in code-projects Web-Based Inventory and POS System 1.0. The impacted element is an unknown function of the file /transaction.php. This manipulation of the argument shopid causes sql injection. The attack is possible to be carried out remotely. The exploit has been publicly disclosed and may be utilized.

References

Community reviews

Loading reviews…