Security readout for executives and security teams
Plain-English summary
This affects WordPress sites using the Custom Post Type to Map Store plugin through version 1.1.0. A malicious website could trick a user into making a change that stores script content, creating persistent cross-site scripting risk. The sources do not identify a patched version or active exploitation.
Executive priority
Treat as a high-priority WordPress plugin exposure if the plugin is present. Prioritize inventory first, then removal, disablement, or vendor-directed remediation.
Technical view
CVE-2024-53769 is a CSRF issue in lriaudel cpt-to-map-store that can lead to stored XSS. CVSS 3.1 is 7.1 high: network attack vector, low complexity, no attacker privileges, user interaction required, and changed scope with low confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to WordPress installations running Custom Post Type to Map Store, package cpt-to-map-store, through version 1.1.0.
Exploitation context
The source data does not show CISA KEV listing or active exploitation. The CVSS vector indicates an attacker needs user interaction, consistent with CSRF leading to stored XSS.
Researcher notes
Public data identifies the weakness class as CWE-352 and the outcome as stored XSS, but does not include vulnerable parameters, proof of concept, exploit telemetry, or a named fixed version.
Mitigation direction
- Inventory WordPress sites for Custom Post Type to Map Store and confirm plugin version.
- Remove or disable the plugin where it is not business-critical.
- If installed at version 1.1.0 or older, check vendor or Patchstack guidance.
- Restrict plugin administration to trusted users until vendor guidance is confirmed.
Validation and detection
- Confirm whether cpt-to-map-store is installed on production and staging WordPress sites.
- Record installed plugin versions and compare against the affected range through 1.1.0.
- Review recent content or plugin configuration changes for unexpected stored script content.
- Check security advisories for a fixed release or vendor-provided mitigation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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.
Open ATT&CK lookupCVE-2024-53769 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7PatchstackVulnerability scoring details
Base CVSS 3.1 score
7.1HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.