CVE-2024-8604
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 classified as problematic has been found in SourceCodester Online Food Ordering System 2.0. This affects an unknown part of the file index.php of the component Create an Account Page. The manipulation of the argument First Name/Last Name leads to cross site scripting. It is possible to initiate the attack remotely.
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 confidenceA stored cross-site scripting (XSS) vulnerability exists in the account registration page (index.php) of SourceCodester Online Food Ordering System 2.0. The First Name and Last Name fields accept unsanitized input, allowing an attacker to inject malicious JavaScript that executes when other users view the registration data.
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= 2.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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 the product and versionIdentify the installed version of SourceCodester/Oretnom23 Online Food Ordering System. Check for files like readme.txt, version.php, or the application header/footer for version strings.Affected if The installed version is 2.0 or the specific version cannot be determined but the product matches.
-
Verify registration functionality is accessibleAccess the registration page (index.php) and confirm the First Name and Last Name input fields are present and functional.Affected if The registration page loads and accepts input in First Name and Last Name fields.
-
Inspect database for stored malicious inputQuery the users or customers database table (typically named 'users', 'customers', or similar) and examine the first_name and last_name columns for any suspicious content containing HTML tags, script elements, or JavaScript event handlers.Affected if Records exist with encoded or raw script tags, event handlers, or HTML in name fields.
-
Check if name fields are displayed elsewhereIdentify all pages that query and display user registration data (such as admin user lists, order details, or public profiles). Inspect the page source to see if the First Name and Last Name values are rendered without encoding.Affected if User-supplied name data is displayed in any page without proper HTML encoding/escaping.
You are affected if you are running version 2.0 of this product, the registration feature is active, and either malicious script tags already exist in stored name fields or the application displays name data without output encoding.
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.
dbcve · scopedImplement input validation to reject special characters and output encoding/escaping when displaying user-supplied name fields to prevent script execution.
- 1. Locate the registration form handler in index.php where First Name and Last Name inputs are processed
- 2. Implement server-side input validation to strip or sanitize special characters (<, >, ", ', javascript:, onerror=, etc.) from the First Name and Last Name fields before storing in database
- 3. Apply output encoding using htmlspecialchars($name, ENT_QUOTES, 'UTF-8') or equivalent when displaying user-supplied name fields in any HTML context
- 4. Implement Content Security Policy (CSP) headers to mitigate XSS by restricting inline scripts
- 5. Consider implementing a web application firewall (WAF) as an additional layer of protection
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-8604 — 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-8604 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