CVE-2024-51644
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in samwilson Addressbook addressbook allows Stored XSS.This issue affects Addressbook: from n/a through <= 1.1.3.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in samwilson Addressbook allows attackers to inject malicious scripts through forged requests, resulting in Stored XSS. The application lacks proper CSRF protection, enabling attackers to trick authenticated users into executing unintended actions that persist malicious content.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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.
-
Identify the Addressbook applicationCheck if the samwilson Addressbook application is deployed in your environment by examining installed web applications, checking for the addressbook directory structure, or reviewing application metadata files for the product name.Affected if The samwilson Addressbook application is present in the environment.
-
Check for CSRF token implementationExamine the application source code or configuration to determine if CSRF tokens are implemented for state-changing operations such as adding, editing, or deleting contacts. Review form submissions and API endpoints for token validation logic.Affected if CSRF tokens are NOT implemented or are missing from state-changing operations.
-
Inspect SameSite cookie attributesReview the application's cookie configuration and session management settings to check if SameSite attributes are properly set on authentication cookies. Use browser developer tools or server logs to examine cookie headers.Affected if SameSite cookie attributes are not configured or are set to 'None' without Secure flags.
-
Test for stored XSS via CSRFCreate a test contact with a script tag payload in a visible field (name, address, notes). Log in as a different user and verify if the malicious script executes when viewing the contact. Alternatively, examine the application's output encoding implementation.Affected if Stored XSS is possible and scripts execute when viewing injected contact data.
You are affected if the samwilson Addressbook is present and CSRF protection is absent or insufficient, allowing stored XSS to persist through forged requests.
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 CSRF tokens for all state-changing operations and add proper input validation with output encoding to prevent stored XSS. Additionally, configure SameSite cookie attributes.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-51644 — 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-51644 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