CVE-2024-1267
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 problematic, has been found in CodeAstro Restaurant POS System 1.0. Affected by this issue is some unknown functionality of the file create_account.php. The manipulation of the argument Full Name leads to cross site scripting. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. VDB-253010 is the identifier assigned to this vulnerability.
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 stored Cross-Site Scripting (XSS) vulnerability exists in CodeAstro Restaurant POS System 1.0 within the create_account.php file. The Full Name parameter is not properly sanitized before being stored and rendered, allowing malicious JavaScript to be executed in the context of other users' browsers.
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
- 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 CodeAstro Restaurant POS System installationLocate the application files on your server. Look for directories containing the restaurant POS system files, typically in the web root. Check for presence of create_account.php file.Affected if The application files and create_account.php exist in your environment
-
Verify the installed versionCheck any version information files (like version.php, readme.txt, or changelog) in the application root directory, or check the source code for version declarations.Affected if The installed version is CodeAstro Restaurant POS System 1.0
-
Inspect the Full Name handling in create_account.phpOpen create_account.php and locate where the Full Name parameter is processed. Look for input handling code (e.g., $_POST['fullname'] or similar) and check if htmlspecialchars(), htmlentities(), or a sanitization function is applied before storing or rendering the value.Affected if The Full Name parameter is stored or rendered without sanitization functions like htmlspecialchars() or htmlentities()
-
Verify the registration functionality is accessibleConfirm that the create_account.php page is accessible to users (not restricted by authentication or network controls). Check if the registration endpoint accepts user input.Affected if Unauthenticated or low-privilege users can access the account creation page and submit the Full Name parameter
You are affected if you have CodeAstro Restaurant POS System version 1.0 installed with the create_account.php file present and the Full Name parameter is not sanitized before storage or display.
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 input validation and output encoding for the Full Name parameter in create_account.php. Use htmlspecialchars() or a proper sanitization library when rendering user-supplied data, and consider implementing a Content Security Policy (CSP) header as a defense-in-depth measure.
- 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-1267 — 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-1267 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