CVE-2025-39435: WordPress My Marginalia plugin <= 1.0.6 - CSRF to Stored XSS vulnerability
Cross-Site Request Forgery (CSRF) vulnerability in davidfcarr My Marginalia my-marginalia allows Stored XSS.This issue affects My Marginalia: from n/a through <= 1.0.6.
Security readout for executives and security teams
Plain-English summary
CVE-2025-39435 affects the WordPress My Marginalia plugin through version 1.0.6. A malicious site could trick an authenticated WordPress user into making an unwanted change that stores script content. That script may later run in a visitor’s browser. This is not listed as known exploited in CISA KEV.
Executive priority
Treat as a near-term WordPress plugin risk where the plugin is present. Prioritize identification and remediation on public-facing or business-critical sites, but do not assume enterprise-wide exposure without confirming plugin deployment.
Technical view
The issue is a CSRF vulnerability leading to stored XSS in davidfcarr My Marginalia/my-marginalia. CVSS 3.1 is 7.1 high: AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L. The CVE cites CWE-352 and affects My Marginalia through <=1.0.6. Public sources provided do not name a patched version.
Likely exposure
Exposure is limited to WordPress sites with the My Marginalia plugin installed at version 1.0.6 or earlier. Sites without this plugin are not affected based on the provided sources.
Exploitation context
The CVSS vector requires user interaction and no attacker privileges. The likely scenario is tricking a logged-in user into an action that stores XSS. No provided source states active exploitation or public weaponization.
Researcher notes
The source bundle is sparse. It identifies CSRF to stored XSS, affected versions through 1.0.6, CVSS 7.1, and Patchstack as the vulnerability database reference. It does not provide root-cause details, patched version, proof-of-concept status, or confirmed exploitation.
Mitigation direction
Inventory WordPress sites for the My Marginalia plugin.
Check installed plugin versions and flag version 1.0.6 or earlier.
Review vendor or Patchstack guidance for an available fix or safe workaround.
If no fix is available, consider disabling the plugin until guidance is confirmed.
Restrict administrative access and reinforce anti-phishing controls for WordPress users.
Validation and detection
Confirm whether My Marginalia is installed on each WordPress site.
Record the installed plugin version from WordPress administration or asset inventory.
Review plugin change history or vendor advisories for a fixed release.
Check web application logs for suspicious administrative actions related to the plugin.
Verify CISA KEV status before declaring active exploitation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · medium confidence lookup
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.
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.
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-352 · source CWE mapping
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.