CVE-2025-6936
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability was found in code-projects Simple Pizza Ordering System 1.0. It has been classified as critical. This affects an unknown part of the file /addpro.php. The manipulation of the argument ID leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA critical SQL injection vulnerability exists in Simple Pizza Ordering System 1.0 in the /addpro.php file. The ID parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject arbitrary SQL commands.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Simple Pizza Ordering System is installedIdentify the web application running on your server. Check for files like index.php, login pages, or application banners that identify the product as 'Simple Pizza Ordering System' by Carmelo. Look for version number '1.0' in source code, changelogs, or admin panels.Affected if The application is identified as Simple Pizza Ordering System version 1.0
-
Locate the vulnerable scriptSearch your web root directory for the file /addpro.php. This file handles product addition functionality and contains the SQL injection point.Affected if The file /addpro.php exists in the web application directory
-
Inspect the ID parameter handling in addpro.phpOpen /addpro.php and examine how the 'id' parameter is handled. Look for SQL query execution (SELECT, INSERT, UPDATE, DELETE statements) that directly incorporates $_GET['id'] or $_POST['id'] without using prepared statements, parameter binding, or input sanitization functions like mysqli_real_escape_string or PDO::prepare.Affected if The code directly uses the 'id' parameter from request input in SQL queries without parameterized queries or escaping functions
-
Verify the application is network accessibleConfirm the web application is accessible over HTTP/HTTPS. The vulnerability is exploitable without authentication, so if the application is publicly accessible, the flaw can be triggered remotely.Affected if The application is reachable over the network and /addpro.php is accessible without authentication
You are affected if Simple Pizza Ordering System version 1.0 is running and the file /addpro.php contains direct SQL query construction using the 'id' parameter without prepared statements.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace dynamic SQL queries with parameterized queries/prepared statements in /addpro.php, implement proper input validation on the ID parameter, and apply principle of least privilege to the database user.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6936 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-6936 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data