Security readout for executives and security teams
Plain-English summary
A WordPress plugin used for push notifications has a CSRF flaw that sources describe as leading to stored XSS in versions through 3.9. An attacker would need to trick a user into interacting with a crafted request, but successful abuse could place malicious script content in the site context. No supplied source confirms active exploitation.
Executive priority
Prioritize identification and remediation on externally reachable WordPress properties, especially ecommerce sites. Treat as high urgency where the plugin is active because stored XSS can affect site trust, users, and administrative sessions.
Technical view
CVE-2024-54386 affects pushmonkey Push Monkey Pro package push-monkey-desktop-push-notifications through version 3.9. The issue is CWE-352 CSRF with CVSS 3.1 score 7.1, vector AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L. The title indicates CSRF to stored XSS, but the provided evidence does not include vulnerable endpoints or fix details.
Likely exposure
Exposure is limited to WordPress sites with Push Monkey Pro - Web Push Notifications and WooCommerce Abandoned Cart installed at version 3.9 or earlier. The bundle marks the default status as unaffected outside the specified affected range.
Exploitation context
The CVSS vector requires user interaction and no attacker privileges. The KEV flag is false, and the supplied sources do not state active exploitation, public exploit availability, or observed attacks.
Researcher notes
The public bundle supports CSRF and stored XSS characterization, CVSS 7.1, and affected versions through 3.9. It does not provide endpoint-level details, exploit telemetry, or a named fixed version, so validation should stay source-driven and avoid assumptions.
Mitigation direction
- Inventory WordPress sites for the Push Monkey Pro plugin and installed version.
- If version is 3.9 or earlier, check vendor or Patchstack guidance for remediation.
- Update to a vendor-confirmed fixed release if one is available.
- Disable or remove the plugin if no safe supported version can be confirmed.
- Review administrative workflows for unexpected stored content changes.
Validation and detection
- Confirm whether push-monkey-desktop-push-notifications is installed on each WordPress site.
- Record plugin versions and compare them against the affected range through 3.9.
- Review Patchstack and CVE records for any updated fix or exploitation notes.
- Check site pages and plugin-managed content for unexpected stored script content.
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-54386 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.