CVE-2025-11424VulnerabilityPublished 8 Oct 2025

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

Affects code-projects Web-Based Inventory and POS SystemSource CVE Database V5

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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
code-projects Web-Based Inventory and POS System	Affected =1.0	Fixed in–

AI-suggested

1. Immediately audit all instances of the code-projects Web-Based Inventory and POS System version 1.0 to identify vulnerable deployments. 2. Implement input validation and sanitization on the emailid parameter in /login.php, ensuring that only valid email formats are accepted. 3. Refactor the database access code to use parameterized queries or prepared statements to prevent SQL injection. 4. If possible, upgrade to a newer, patched version of the software once available or apply vendor-provided patches promptly. 5. Employ Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the emailid parameter. 6. Monitor database logs and application logs for unusual queries or failed login attempts indicative of exploitation attempts. 7. Conduct regular security assessments and penetration testing focusing on input validation and authentication mechanisms. 8. Educate IT and security teams about this vulnerability and ensure incident response plans include steps for SQL injection attacks. 9. Isolate vulnerable systems from critical networks until mitigations are applied to reduce potential lateral movement. 10. Review and enhance overall application security posture, including secure coding training for developers.

Description

A vulnerability was determined in code-projects Web-Based Inventory and POS System 1.0. This impacts an unknown function of the file /login.php. Executing manipulation of the argument emailid can lead to sql injection. The attack may be performed from remote. The exploit has been publicly disclosed and may be utilized.

Impact

For European organizations, especially SMEs and retailers relying on the code-projects Web-Based Inventory and POS System, this vulnerability poses significant risks. Exploitation could lead to unauthorized access to sensitive customer and business data, including sales records, inventory details, and potentially payment information if stored. This can result in data breaches violating GDPR requirements, leading to regulatory fines and reputational damage. Integrity of inventory and sales data could be compromised, causing financial discrepancies and operational disruptions. Availability of the POS system could also be affected if attackers execute destructive SQL commands, impacting business continuity. The remote and unauthenticated nature of the exploit increases the attack surface, making it easier for cybercriminals to target vulnerable systems across Europe. Although no active exploits are reported, the public disclosure heightens the urgency for European organizations to assess their exposure and implement mitigations to prevent potential exploitation and associated financial and legal consequences.

Summary

CVE-2025-11424 is a SQL injection vulnerability identified in version 1.0 of the code-projects Web-Based Inventory and POS System, specifically in the /login.php script. The vulnerability arises from improper sanitization and validation of the emailid parameter, which is used in SQL queries without adequate protection. An attacker can remotely manipulate this parameter to inject malicious SQL code, potentially allowing unauthorized access to the database, extraction or modification of sensitive data, or disruption of service. The vulnerability requires no authentication or user interaction, making it exploitable over the network by any remote attacker. The CVSS 4.0 base score is 6.9 (medium severity), reflecting the ease of exploitation and the potential impact on confidentiality, integrity, and availability, though the impact is limited to the affected system without scope extension. No patches or fixes have been published yet, and no known exploits are currently active in the wild, but public disclosure increases the risk of exploitation attempts. The vulnerability affects only version 1.0 of the product, which is a web-based inventory and POS system used primarily by small to medium enterprises to manage sales and inventory data. The lack of secure coding practices in handling user input in login functionality is the root cause. Remediation involves applying secure coding techniques such as parameterized queries or prepared statements, input validation, and possibly updating or replacing the affected software component.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Oct 2025, 02:30 UTC

Technical details

References

Community reviews

Related threats