CVE-2026-13571
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 flaw has been found in SourceCodester Simple Food Ordering System 1.0. The affected element is an unknown function of the file /cart.php. Executing a manipulation of the argument item_price can lead to business logic errors. The attack may be performed from remote. The exploit has been published 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 · moderate confidenceThe SourceCodester Simple Food Ordering System 1.0 contains a business logic vulnerability in /cart.php where the item_price parameter can be manipulated by an attacker. This allows price tampering in the shopping cart, likely enabling items to be purchased at attacker-controlled prices rather than legitimate server-defined prices.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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 SourceCodester Simple Food Ordering System installationLocate the web application root directory and identify if the Simple Food Ordering System is deployed. Check for characteristic files such as index.php, cart.php, or a folder named 'simple-food-ordering-system'.Affected if The application is present and accessible on the server
-
Verify cart.php exists and is accessibleCheck if /cart.php exists in the web root and is accessible via HTTP/HTTPS request. Attempt a baseline request to confirm the file handles cart operations.Affected if cart.php is found and responds to requests
-
Inspect cart.php for item_price parameter handlingExamine the source code of cart.php to identify if it accepts an item_price parameter from client-side input (POST or GET). Search for code patterns like $_POST['item_price'], $_GET['item_price'], or similar client-supplied price variables.Affected if cart.php accepts and uses a client-supplied item_price without server-side validation
-
Check if price validation against database is missingReview cart.php code to determine whether it fetches item prices from the database (e.g., SELECT price FROM menu_items WHERE...) or if it relies solely on the client-provided item_price value for cart calculations.Affected if The code does not validate item_price against authoritative database pricing before using it in cart totals
-
Test the vulnerable parameter if authorizedIf you have authorization, submit a test order with a manipulated item_price parameter (e.g., set price to 0.01) and observe whether the cart accepts the altered price for total calculation.Affected if The system accepts and processes the manipulated price, allowing items to be added at attacker-defined prices
A user is affected if the Simple Food Ordering System 1.0 is deployed and cart.php accepts item_price from client input without validating it against server-defined pricing from the database.
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 dataImplement server-side price validation by fetching item prices from the database rather than trusting client-supplied item_price parameters. Add完整性 checks to ensure submitted prices match authoritative pricing data.
- 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-2026-13571 — 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-2026-13571 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