CVE-2025-14959VulnerabilityPublished 19 Dec 2025Updated 24 Feb 2026

CVE-2025-14959: 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, 08:30 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 32% 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 19 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 26 Oct 2026.

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 Simple Stock System	Affected =1.0	Fixed in–

AI-suggested

To mitigate CVE-2025-14959, organizations should immediately review and update the affected Simple Stock System software. Since no official patches are currently available, the following specific measures are recommended: 1) Implement input validation and sanitization on the 'Username' parameter to reject or properly encode malicious input. 2) Refactor database queries to use parameterized prepared statements or stored procedures to prevent direct injection of user input into SQL commands. 3) Employ web application firewalls (WAFs) with rules targeting SQL injection patterns to detect and block exploit attempts at the network perimeter. 4) Conduct thorough code audits and penetration testing focusing on input handling in all user-facing endpoints. 5) Monitor application logs and database activity for unusual queries or access patterns indicative of exploitation attempts. 6) Consider isolating the affected application environment and restricting database permissions to minimize potential damage. 7) Stay informed on vendor updates or community patches and apply them promptly once available. These targeted actions go beyond generic advice by focusing on the specific vulnerable parameter and practical controls to reduce risk until an official patch is released.

Description

A weakness has been identified in code-projects Simple Stock System 1.0. This issue affects some unknown processing of the file /market/signup.php. Executing a manipulation of the argument Username can lead to sql injection. The attack may be launched remotely. The exploit has been made available to the public and could be used for attacks.

Impact

The SQL injection vulnerability in Simple Stock System 1.0 can have significant impacts on organizations using this software. Successful exploitation can lead to unauthorized disclosure of sensitive business data, including user credentials, stock inventory details, and transactional records, compromising confidentiality. Attackers may also alter or delete data, affecting data integrity and potentially disrupting business operations. In some cases, attackers could execute administrative commands on the database, leading to denial of service or further system compromise. Since the vulnerability requires no authentication or user interaction, the attack surface is broad, increasing the risk of automated exploitation attempts. Organizations could face financial losses, reputational damage, and regulatory penalties if sensitive data is exposed or operations are disrupted. The medium severity rating reflects these risks, but the availability of public exploits and absence of patches could escalate the threat if not addressed promptly.

Summary

CVE-2025-14959 identifies a SQL injection vulnerability in the Simple Stock System version 1.0 developed by code-projects. The vulnerability exists in the /market/signup.php endpoint, where the 'Username' parameter is improperly sanitized or validated, allowing an attacker to inject arbitrary SQL commands. This injection flaw can be exploited remotely without requiring authentication or user interaction, making it accessible to a wide range of attackers. The vulnerability could allow attackers to extract sensitive data, modify database contents, or disrupt system operations by executing crafted SQL queries. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P) indicates network attack vector, low attack complexity, no privileges or user interaction needed, and partial impacts on confidentiality, integrity, and availability. Although no active exploits have been reported in the wild, the public availability of exploit code increases the likelihood of exploitation attempts. The lack of official patches or mitigation guidance from the vendor further elevates the risk for organizations relying on this software. The vulnerability highlights the critical need for secure coding practices, especially input validation and parameterized queries, in web applications handling stock or inventory data.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Feb 2026, 23:07 UTC

Technical details

References

Community reviews

Related threats