CVE-2024-1024
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 has been found in SourceCodester Facebook News Feed Like 1.0 and classified as problematic. This vulnerability affects unknown code of the component New Account Handler. The manipulation of the argument First Name/Last Name with the input <script>alert(1)</script> leads to cross site scripting. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-252292.
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 the New Account Handler component of SourceCodester Facebook News Feed Like 1.0. The First Name and Last Name fields during account registration accept unsanitized input, allowing injection of malicious scripts (e.g., <script>alert(1)</script>) that execute when other users view the account profile.
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 Facebook News Feed Like is installedLocate the web application directory or check the application's main page to identify if this specific SourceCodester application is runningAffected if The application Oretnom23 Facebook News Feed Like version 1.0 is present in the environment
-
Verify the application versionCheck the application's version information, typically found in an about page, footer, or version configuration fileAffected if The installed version is exactly 1.0 (the only affected version per the CVE)
-
Confirm account registration is enabledAccess the registration page (typically /register or similar path) to determine if new user accounts can be createdAffected if Registration functionality is accessible and enabled for users
-
Inspect First Name and Last Name input handlingExamine the New Account Handler component source code (likely a PHP file handling registration) for how the first_name and last_name parameters are processed - look for whether sanitization functions like htmlspecialchars, strip_tags, or similar are applied before database storageAffected if No server-side input validation or sanitization is performed on these fields before storage
-
Verify profile viewing is accessible to other usersCheck if registered user profiles are viewable by other authenticated users or publicly accessible - test by creating a test account and attempting to view it from a different user sessionAffected if User profiles with the injected name fields are viewable by other users, completing the stored XSS attack vector
The environment is affected if Facebook News Feed Like version 1.0 is installed with registration enabled, and the First Name/Last Name fields lack server-side sanitization in the New Account Handler, allowing stored XSS to execute when other users view the profile.
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 server-side input validation and output encoding/sanitization for the First Name and Last Name fields. Use context-aware escaping when displaying user-supplied data and consider implementing a Content Security Policy (CSP) header.
- 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-1024 — 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-1024 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