CVE-2024-8559
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, which was classified as critical, has been found in SourceCodester Online Food Menu 1.0. This issue affects some unknown processing of the file /endpoint/delete-menu.php. The manipulation of the argument menu leads to sql injection. The attack may be initiated 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 confidenceSQL injection vulnerability in SourceCodester Online Food Menu 1.0 allows remote attackers to manipulate the 'menu' parameter in /endpoint/delete-menu.php to inject malicious SQL queries. The lack of input sanitization or parameterized queries in the delete-menu endpoint enables attackers to potentially access, modify, or delete database contents.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 installed product versionIdentify the SourceCodester Online Food Menu version installed in your environment. Check any version files, headers, or the application's about/page to determine if it is version 1.0.Affected if The installed version is Remyandrade Online Food Menu 1.0 exactly.
-
Locate the vulnerable endpoint fileVerify that the file /endpoint/delete-menu.php exists in your web application's directory structure.Affected if The file /endpoint/delete-menu.php is present on the server.
-
Inspect the delete-menu.php code for dynamic SQLOpen /endpoint/delete-menu.php and examine the database query code. Look for SQL statements that concatenate or embed the 'menu' parameter directly into the query string without using prepared statements or parameter binding.Affected if The code contains dynamic SQL queries using the 'menu' parameter without prepared statements or parameterized queries.
-
Verify input validation is absentReview the same file to determine whether the 'menu' parameter undergoes any sanitization, validation, or type checking before being used in the SQL query.Affected if There is no input sanitization, validation, or escaping applied to the 'menu' parameter before database operations.
If you are running version 1.0 of Remyandrade Online Food Menu and the endpoint /endpoint/delete-menu.php contains unsanitized dynamic SQL using the 'menu' parameter, your environment is affected by CVE-2024-8559.
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 in delete-menu.php with prepared statements/parameterized queries, and implement proper input validation on the 'menu' parameter before database operations.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-8559 — 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-2024-8559 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