CVE-2025-6483VulnerabilityPublished 22 Jun 2025

CVE-2025-6483: code-projects Simple Pizza Ordering System · SQL Injection

Affects code-projects Simple Pizza Ordering 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 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 22 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 Simple Pizza Ordering System	Affected =1.0	Fixed in–

AI-suggested

1. Immediate code review and sanitization: Organizations should audit the /edituser.php script to implement parameterized queries or prepared statements for all database interactions involving user-supplied input, specifically the 'ID' parameter. 2. Input validation: Enforce strict server-side validation to ensure that 'ID' parameters conform to expected formats (e.g., numeric only) before processing. 3. Web Application Firewall (WAF): Deploy or update WAF rules to detect and block SQL injection patterns targeting the vulnerable endpoint. 4. Network segmentation: Restrict external access to the ordering system's administrative interfaces to trusted IP ranges or VPN connections. 5. Monitoring and logging: Enable detailed logging of database queries and web requests to detect anomalous activities indicative of exploitation attempts. 6. Incident response readiness: Prepare to isolate affected systems and conduct forensic analysis if exploitation is suspected. 7. Vendor engagement: Contact the vendor or community maintaining the Simple Pizza Ordering System to request official patches or updates. 8. Alternative solutions: Consider migrating to more secure, actively maintained ordering platforms if remediation is not feasible. 9. Regular backups: Maintain frequent, secure backups of the database to enable recovery in case of data tampering or loss.

Description

A vulnerability has been found in code-projects Simple Pizza Ordering System 1.0 and classified as critical. Affected by this vulnerability is an unknown functionality of the file /edituser.php. The manipulation of the argument ID leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.

Impact

For European organizations using the Simple Pizza Ordering System 1.0, this vulnerability poses a significant risk to customer data confidentiality and business continuity. Exploitation could lead to unauthorized disclosure of personal customer information, including order details and user credentials if stored insecurely. Data integrity could be compromised by unauthorized modification or deletion of records, impacting order fulfillment and financial transactions. Availability may also be affected if attackers execute destructive queries or cause database crashes. Small and medium-sized enterprises (SMEs) in the food service sector, which often rely on off-the-shelf or open-source ordering systems, are particularly vulnerable due to limited cybersecurity resources. Additionally, compromised systems could be leveraged as entry points for broader network intrusions, threatening supply chain partners and payment processing systems. The public disclosure of the exploit increases the risk of opportunistic attacks, especially in countries with high densities of hospitality businesses. Regulatory implications under GDPR are also a concern, as data breaches involving personal data could result in significant fines and reputational damage.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 22 Jun 2025, 16:19 UTC

Technical details

References

Community reviews

Related threats