Security readout for executives and security teams
Plain-English summary
CVE-2024-51649 affects the WordPress Mobilize plugin through version 3.0.7. A malicious site or link could cause a logged-in WordPress user to make an unintended change that stores script content, enabling stored XSS. The sources do not show known active exploitation or a named fixed version.
Executive priority
Treat this as a high-priority WordPress plugin exposure where Mobilize is installed. Prioritize public websites, administrator-heavy sites, and environments without strong change monitoring. Do not claim emergency exploitation unless new evidence appears.
Technical view
The issue is a CSRF vulnerability in Patrick Lumumba Mobilize that can lead to stored cross-site scripting. CVSS 3.1 is 7.1 high, with network access, low complexity, no attacker privileges, and required user interaction. Scope is changed, with low confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to WordPress sites with the Mobilize plugin installed at version 3.0.7 or earlier. The provided sources do not identify other affected products or platforms.
Exploitation context
The source bundle marks KEV as false, and no cited source states active exploitation. Practical exploitation appears to require user interaction, consistent with CSRF, likely involving a logged-in WordPress user.
Researcher notes
The evidence supports CSRF leading to stored XSS, but does not provide patch details, exploit activity, or deeper root-cause mechanics. Validation should focus on plugin presence, affected version confirmation, and suspicious stored content or settings changes.
Mitigation direction
- Inventory WordPress sites for the Mobilize plugin and installed version.
- Disable or remove Mobilize where it is not operationally required.
- Check vendor or Patchstack guidance for an official fixed version or workaround.
- Apply an official update when one is available and verified.
- Limit WordPress administrator sessions and enforce least-privilege admin access.
Validation and detection
- Confirm whether Mobilize is installed on each WordPress property.
- Verify installed versions are not 3.0.7 or earlier.
- Review recent Mobilize-related settings or content changes for unexpected script content.
- Check security monitoring for suspicious WordPress admin actions around the disclosure period.
- Document exceptions where no vendor fix is currently identified.
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-51649 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
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/Wordpress/Plugin/mobilize/vulnerability/wordpress-mobilize-plugin-3-0-7-csrf-to-stored-cross-site-scripting-xss-vulnerability?_s_id=cveCVE reference, Patchstack · vdb-entry
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.