CVE-2025-6307VulnerabilityPublished 20 Jun 2025

CVE-2025-6307: code-projects Online Shoe Store · SQL Injection

Affects code-projects Online Shoe StoreSource 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 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 20 Jun 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 Online Shoe Store	Affected =1.0	Fixed in–

AI-suggested

1. Immediate code review and input validation: Implement strict server-side input validation and sanitization for all user-supplied parameters, especially 'firstname' and other parameters in /function/edit_customer.php, using parameterized queries or prepared statements to prevent SQL injection. 2. Apply Web Application Firewall (WAF) rules: Deploy or update WAFs to detect and block SQL injection patterns targeting the vulnerable endpoint. 3. Restrict database permissions: Ensure the database user account used by the application has the minimum necessary privileges, limiting potential damage from injection attacks. 4. Monitor logs and network traffic: Set up enhanced logging and anomaly detection to identify suspicious activities related to the vulnerable endpoint. 5. Isolate affected systems: If possible, isolate or limit external access to the vulnerable application until a patch or secure update is available. 6. Engage with vendor or community: Monitor for official patches or community-provided fixes and apply them promptly once available. 7. Conduct security awareness: Inform development and operations teams about the vulnerability and best practices to prevent similar issues in future releases.

Description

A vulnerability was found in code-projects Online Shoe Store 1.0. It has been rated as critical. This issue affects some unknown processing of the file /function/edit_customer.php. The manipulation of the argument firstname leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. Other parameters might be affected as well.

Impact

For European organizations using the code-projects Online Shoe Store 1.0 platform, this vulnerability poses a significant risk to customer data security and business operations. Successful exploitation could lead to unauthorized disclosure of sensitive customer information, including personal details, which may violate GDPR and other data protection regulations, resulting in legal and financial penalties. Data integrity could be compromised, leading to corrupted order records or manipulated customer profiles, undermining trust and operational reliability. Availability of the e-commerce service could also be affected if attackers execute destructive SQL commands or cause database outages. Given the remote and unauthenticated nature of the attack, threat actors could automate exploitation attempts at scale, targeting multiple deployments across Europe. This is particularly concerning for small to medium-sized enterprises (SMEs) that may lack robust security monitoring or incident response capabilities. The absence of patches necessitates immediate risk mitigation to prevent data breaches and service disruptions.

Summary

CVE-2025-6307 is a SQL Injection vulnerability identified in version 1.0 of the code-projects Online Shoe Store application. The vulnerability arises from improper sanitization and validation of the 'firstname' parameter in the /function/edit_customer.php script. An attacker can remotely manipulate this parameter to inject malicious SQL code, potentially altering the intended SQL queries executed by the backend database. This can lead to unauthorized data access, data modification, or deletion, compromising the confidentiality, integrity, and availability of the underlying database. The vulnerability does not require authentication or user interaction, and the attack vector is network-based, making exploitation feasible remotely without prior access. While the CVSS 4.0 base score is 6.9 (medium severity), the exploitability is relatively straightforward due to low attack complexity and no privileges required. The vulnerability may also affect other parameters within the same script, increasing the attack surface. No official patches or mitigations have been published at the time of disclosure, and no known exploits have been observed in the wild yet. However, public disclosure of the exploit details increases the risk of imminent exploitation attempts.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 20 Jun 2025, 05:02 UTC

Technical details

References

Community reviews

Related threats