CVE-2024-8562
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 was found in SourceCodester PHP CRUD 1.0 and classified as problematic. Affected by this issue is some unknown functionality of the file /endpoint/Add.php. The manipulation of the argument first_name/middle_name/last_name leads to cross site scripting. The attack may be launched 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 · moderate confidenceA stored XSS vulnerability exists in SourceCodester PHP CRUD 1.0 where the first_name, middle_name, and last_name parameters in /endpoint/Add.php are not properly sanitized before being stored and rendered, allowing injection of malicious JavaScript that executes in the browsers of users viewing the affected 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= 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 the application is SourceCodester PHP CRUDReview your installed web applications and identify if SourceCodester PHP CRUD is deployed. Check application files, documentation, or web server configuration for the product name.Affected if The application is not SourceCodester PHP CRUD, then this CVE does not apply.
-
Verify the installed version is 1.0Locate version information in the application source code, such as in a README file, config file, or header/comment in PHP files. Compare your version against the affected range: Rems Php Crud = 1.0.Affected if The installed version is 1.0, proceed to next check. If version differs, this specific CVE may not apply.
-
Check if the vulnerable endpoint existsInspect your application directory structure for the file /endpoint/Add.php. This file handles the Add functionality where name parameters are processed.Affected if The file /endpoint/Add.php exists and is accessible, proceed to next check.
-
Inspect name field handling for lack of sanitizationReview the source code of /endpoint/Add.php and any related display/rendering files. Look for the handling of first_name, middle_name, and last_name parameters. Check if these fields are used directly in SQL queries without sanitization, or rendered in HTML without output encoding.Affected if The code shows that name parameters are stored or displayed without sanitization functions (such as htmlspecialchars, htmlentities, or parameterized queries), the application is vulnerable.
-
Verify the attack surface existsIf you have access to the application, navigate to the functionality that allows adding or viewing user records containing name fields. Determine if these fields are visible to other users (stored XSS requires the malicious input to be stored and viewed by victims).Affected if The name fields are stored and rendered for other users to see, the stored XSS can be exploited.
A user is affected if they are running SourceCodester PHP CRUD version 1.0, the /endpoint/Add.php file exists, and name fields are stored and rendered without sanitization or 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.
From vendor dataImplement input validation and output encoding/escaping on all user-supplied name fields before storage and before rendering. Additionally, configure Content Security Policy (CSP) headers to mitigate XSS attacks.
- 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-2024-8562 — 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-8562 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