Security readout for executives and security teams
Plain-English summary
This vulnerability affects the WordPress PPO Call To Actions plugin through version 0.1.3. A malicious site could abuse a logged-in user’s browser to change plugin-managed content, potentially storing script in the site. That creates business risk for visitor trust, account security, and site integrity.
Executive priority
Treat this as a high-priority WordPress plugin exposure. Prioritize externally facing sites and any site handling customer, payment, or lead data. If the plugin is unused or unfixed, removal is the lowest-friction risk reduction path.
Technical view
Sources describe a CSRF issue in ppo-call-to-actions through 0.1.3, titled as CSRF to stored XSS. The CVSS 3.1 score is 7.1, network exploitable with low complexity and required user interaction. Attacker privileges are not required, but exploitation depends on a victim interaction path.
Likely exposure
Exposure is likely limited to WordPress sites that have PPO Call To Actions installed at version 0.1.3 or earlier. The source bundle does not identify other affected products or platforms.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no source here confirms active exploitation. The risk is credible because CSRF can cause trusted browser actions, and stored XSS can persist for later visitors.
Researcher notes
The evidence is sparse. The bundle supports CSRF in PPO Call To Actions through 0.1.3 and the title indicates stored XSS, but no exploit details, patch version, or active exploitation confirmation are provided.
Mitigation direction
- Inventory WordPress sites for PPO Call To Actions plugin usage.
- Update the plugin if vendor guidance identifies a fixed version.
- Disable or remove the plugin where no fixed release is available.
- Review Patchstack and CVE records for updated remediation guidance.
- Limit WordPress admin access to necessary trusted users.
Validation and detection
- Check installed plugin versions against affected range through 0.1.3.
- Confirm whether a vendor-fixed version is available before upgrade approval.
- Review plugin-managed content for unexpected scripts or HTML.
- Check WordPress logs for suspicious plugin administration activity.
- Document removal, upgrade, or accepted risk for each affected site.
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-2025-24001 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/ppo-call-to-actions/vulnerability/wordpress-ppo-call-to-actions-plugin-0-1-3-csrf-to-stored-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.