Security readout for executives and security teams
Plain-English summary
This affects the WordPress Addressbook plugin through version 1.1.3. A malicious site could cause a logged-in user to create stored script content in the plugin, which may later run in visitors' browsers. The business risk is site compromise symptoms, user data exposure, and reputational damage if the plugin is installed.
Executive priority
Treat as a high-priority WordPress plugin exposure if Addressbook is installed. Prioritize inventory first, then update, disable, or remove based on vendor guidance. No source provided here confirms active exploitation.
Technical view
CVE-2024-51644 is a CSRF vulnerability in samwilson Addressbook for WordPress that can lead to stored XSS. The CVSS 3.1 score is 7.1 with network attack vector, low complexity, no attacker privileges, required user interaction, changed scope, and low confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to WordPress sites using the Addressbook plugin at version 1.1.3 or earlier, based on the provided description. Sites not running this plugin are not indicated as affected by the source bundle.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVSS vector indicates exploitation requires user interaction, consistent with CSRF-driven stored XSS risk. No exploit details should be assumed from the available evidence.
Researcher notes
Evidence is concise and mainly identifies CSRF to stored XSS in Addressbook through 1.1.3. The provided affected metadata is sparse, and the bundle does not name a fixed version, workaround, proof of exploitation, or detailed vulnerable endpoint.
Mitigation direction
Inventory WordPress sites for the Addressbook plugin and installed version.
Check vendor or Patchstack guidance for a fixed release or official workaround.
Update the plugin if an official fixed version is available.
Disable or remove the plugin if no supported fix is available.
Review affected sites for unexpected Addressbook content changes.
Validation and detection
Confirm whether Addressbook version 1.1.3 or earlier is installed.
Verify remediation by checking the installed plugin version after update or removal.
Review WordPress admin activity for unexpected Addressbook modifications.
Monitor the CVE and Patchstack entries for updated affected or fixed-version details.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-352 · source CWE mapping
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.