CVE-2025-15243VulnerabilityPublished 30 Dec 2025Updated 24 Feb 2026

CVE-2025-15243: code-projects Simple Stock System · SQL Injection

Affects code-projects Simple Stock SystemSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 06:26 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 41% 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 30 Dec 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-26.

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
GitHubc13641462064-lgtm/sql_injection`pkg:github/c13641462064-lgtm/sql_injection`Other threats	Affected =1.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2025-15243, organizations should immediately implement input validation and sanitization on all user-supplied data, especially the Username parameter in /market/login.php. Employing parameterized queries or prepared statements will effectively prevent SQL injection by separating code from data. Restrict database user permissions to the minimum necessary to limit the impact of any successful injection. If an official patch becomes available from code-projects, it should be applied promptly. In the absence of a patch, consider deploying Web Application Firewalls (WAFs) with rules to detect and block SQL injection attempts targeting the login endpoint. Regularly audit logs for suspicious login attempts or unusual database errors. Additionally, conduct security code reviews and penetration testing to identify and remediate similar injection flaws elsewhere in the application. Educate developers on secure coding practices to prevent future vulnerabilities.

Description

A flaw has been found in code-projects Simple Stock System 1.0. This affects an unknown function of the file /market/login.php. Executing a manipulation of the argument Username can lead to sql injection. The attack can be launched remotely. The exploit has been published and may be used.

Impact

The SQL injection vulnerability in Simple Stock System 1.0 can lead to unauthorized disclosure of sensitive information stored in the backend database, such as user credentials or stock data. Attackers may also alter or delete data, undermining data integrity and potentially causing operational disruptions. Availability could be affected if injected queries cause database errors or crashes. Since the vulnerability requires no authentication and can be exploited remotely, it poses a significant risk to any organization using this software, especially those managing critical inventory or stock data. The medium severity rating reflects a moderate impact, but the presence of published exploit code elevates the urgency for remediation. Organizations could face data breaches, financial losses, and reputational damage if exploited. The scope is limited to installations of this specific software version, but similar vulnerabilities in comparable systems could compound risks.

Summary

CVE-2025-15243 is a SQL injection vulnerability identified in version 1.0 of the Simple Stock System developed by code-projects. The vulnerability resides in the /market/login.php script, where the Username parameter is not properly sanitized before being incorporated into SQL queries. This lack of input validation allows an attacker to inject malicious SQL code remotely, without requiring authentication or user interaction. The injection can manipulate backend database queries, potentially enabling unauthorized access to sensitive data, alteration of database contents, or disruption of service. The vulnerability has a CVSS 4.0 score of 6.9, indicating a medium severity level, with an attack vector that is network-based and requires no privileges or user interaction. The impact on confidentiality, integrity, and availability is limited but non-negligible, as the attacker can partially compromise these aspects by exploiting the injection. Although no active exploitation has been reported, the public availability of exploit code increases the likelihood of attacks. The vulnerability affects only version 1.0 of the Simple Stock System, which is a niche inventory management application. No official patches have been linked yet, so mitigation relies on secure coding practices and defensive controls.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Feb 2026, 22:41 UTC

Technical details

References

Community reviews

Related threats