CVE-2024-51031
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 Cross-site Scripting (XSS) vulnerability in manage_account.php in Sourcecodester Cab Management System 1.0 allows remote authenticated users to inject arbitrary web scripts via the "First Name," "Middle Name," and "Last Name" fields.
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 manage_account.php of Sourcecodester Cab Management System 1.0. Authenticated users can inject arbitrary JavaScript through the First Name, Middle Name, and Last Name fields, which executes when other users view the account information.
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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 Cab Management System versionLocate the application version identifier in the source code, admin dashboard, or about page. Check for version strings such as '1.0' in any configuration file, footer, or metadata.Affected if The installed version is Cab Management System 1.0 from Oretnom23.
-
Verify manage_account.php existsCheck the web server document root for the presence of the file manage_account.php. This file is part of the admin/user management functionality.Affected if The file manage_account.php exists in the application directory.
-
Confirm authenticated access to account managementLog into the application with valid user credentials. Navigate to the account management or profile settings area where First Name, Middle Name, and Last Name fields can be edited.Affected if Authenticated users can access the account modification interface with name fields.
-
Check if account information is visible to other usersAs a different authenticated user, locate a page where user profiles or account details are displayed (such as a driver list, user directory, or booking details). Observe whether name fields from other accounts are rendered.Affected if The application displays user name fields to other authenticated users without visible sanitization.
-
Inspect HTML output for name field renderingView the page source or intercept the HTTP response when viewing account information. Examine how the First Name, Middle Name, and Last Name values are rendered in the HTML.Affected if The name values appear as raw, unescaped text in the HTML output (e.g., <td>John</td> instead of <script>...</script>).
If running Cab Management System 1.0 with accessible manage_account.php and users can view each other's account names without encoding, the environment is affected by this stored XSS.
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 to reject malicious payloads and apply proper HTML encoding/escaping when displaying user-supplied name fields to prevent script execution.
- 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-51031 — 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-51031 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