CVE-2025-11604
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 determined in projectworlds Online Ordering Food System 1.0. This issue affects some unknown processing of the file /all-orders.php. This manipulation of the argument Status causes sql injection. Remote exploitation of the attack is possible. The exploit has been publicly disclosed and may be utilized.
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 confidenceSQL injection vulnerability in projectworlds Online Ordering Food System 1.0 allows remote attackers to execute arbitrary SQL commands via the Status parameter in /all-orders.php. The lack of parameterized queries or input sanitization enables attackers to manipulate database queries.
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 the application is installedLocate the file /all-orders.php in the web root directory of the projectworlds Online Ordering Food SystemAffected if The file exists in the web application directory
-
Verify the product versionCheck the version of the installed projectworlds Online Ordering Food System. If no version file is found, cross-reference the application's build or release metadata with version 1.0Affected if The installed version is projectworlds Online Ordering Food System 1.0
-
Examine the SQL query handling in all-orders.phpOpen /all-orders.php and inspect the code for dynamic SQL queries that incorporate the Status parameter without using prepared statements or parameter bindingAffected if The code contains SQL queries that directly concatenate or insert the Status parameter into query strings without sanitization or parameterized queries
-
Check for input validation on the Status parameterSearch the all-orders.php file for any input validation, sanitization, or type checking applied to the Status parameter before using it in database queriesAffected if No input validation or sanitization is performed on the Status parameter before it is used in SQL queries
-
Confirm the vulnerability is exploitableIf the Status parameter is processed through $_GET or $_POST and used in SQL queries without prepared statements, the application is vulnerable to SQL injectionAffected if The Status parameter is passed from user input directly into SQL queries without prepared statements
The environment is affected if the projectworlds Online Ordering Food System version 1.0 is installed and the /all-orders.php file contains SQL queries that use the Status parameter without parameterized queries or input sanitization.
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 prepared statements/parameterized queries, implement strict input validation on the Status parameter, and apply least-privilege database accounts to limit impact of potential compromise.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11604 — 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-11604 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