Security readout for executives and security teams
Plain-English summary
Revision Diet, a WordPress plugin, has a CSRF flaw that can lead to stored cross-site scripting. In practical terms, a tricked site user could cause malicious script to be saved in the site. This can affect confidentiality, integrity, and availability at a limited level.
Executive priority
Treat as a high-priority WordPress plugin exposure where the plugin is installed. Prioritize public or business-critical sites first, especially those with multiple administrators or weak admin session controls.
Technical view
CVE-2025-39419 affects Revision Diet through version 1.0.1. The CVE describes CWE-352 CSRF leading to stored XSS, with CVSS 3.1 score 7.1: network-reachable, low complexity, no privileges, user interaction required, and changed scope.
Likely exposure
Exposure is likely limited to WordPress sites that installed David Miller's Revision Diet plugin at version 1.0.1 or earlier. The source bundle does not provide CPEs or deployment prevalence.
Exploitation context
The source bundle does not show CISA KEV listing or cited active exploitation. The CVSS vector indicates exploitation requires user interaction, consistent with a CSRF-driven stored XSS scenario.
Researcher notes
Evidence is limited to the CVE record and Patchstack VDB reference in the bundle. The affected range is through 1.0.1, but the bundle does not name a fixed version, public exploit, or detailed vulnerable endpoint.
Mitigation direction
- Inventory WordPress sites for the Revision Diet plugin and its version.
- Check vendor, WordPress plugin, and Patchstack guidance for a fixed release.
- If no fixed release exists, disable or remove the plugin where feasible.
- Review WordPress admin access and reduce unnecessary privileged accounts.
- Monitor site content and admin activity for unexpected script changes.
Validation and detection
- Confirm whether Revision Diet is installed on each WordPress instance.
- Record installed plugin versions and flag 1.0.1 or earlier.
- Check security advisories for any vendor-confirmed fixed version.
- Review web logs and CMS audit data for suspicious admin-triggered changes.
- Verify compensating controls do not rely on the vulnerable plugin behavior.
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-39419 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/revision-diet/vulnerability/wordpress-revision-diet-plugin-1-0-1-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.