dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-39435

HIGH · 7.1 CVSS v3.1 Published 2025-04-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A CSRF vulnerability in the My Marginalia WordPress plugin (versions <=1.0.6) allows attackers to craft malicious requests that, when triggered by an authenticated administrator, inject and store XSS payloads into the plugin's data storage. The lack of anti-CSRF tokens on state-changing forms enables attackers to trick logged-in users into unknowingly executing the attack.

MitigationImplement anti-CSRF tokens (nonces) on all forms and AJAX actions, and apply proper input sanitization and output encoding to prevent Stored XSS. Update to the patched version when available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check the installed version of My Marginalia plugin
    In WordPress admin, go to Plugins > Installed Plugins and find 'My Marginalia' in the list. The version number is displayed below the plugin name. Alternatively, check the plugin's main PHP file for the 'Version' header comment.
    Affected if The version is 1.0.6 or lower (any version up to and including 1.0.6)
  2. Verify the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and confirm My Marginalia is currently activated (not just installed).
    Affected if The plugin is activated on the site
  3. Inspect plugin settings for suspicious script content
    Navigate to the My Marginalia plugin settings page in WordPress admin. Examine any text fields, textarea inputs, or stored options for unexpected script tags (such as <script>, <img onerror=, javascript:, or similar XSS vectors). Check the wp_options table in the database for my_marginalia related entries if direct database access is available.
    Affected if Any stored XSS payloads (malicious script tags) are found in plugin settings or database entries
  4. Review plugin PHP files for nonce validation
    Access the plugin files via FTP or file manager. Open the main plugin PHP file and any files handling form submissions or AJAX actions. Search for occurrences of 'wp_verify_nonce', 'check_admin_referer', or 'check_ajax_referer' to verify nonce verification is present.
    Affected if State-changing forms or AJAX actions lack nonce verification (the plugin does not validate anti-CSRF tokens)

Your environment is affected if My Marginalia plugin version is 1.0.6 or lower AND the plugin is active AND either malicious XSS content exists in stored settings OR the plugin lacks nonce validation on forms.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens (nonces) on all forms and AJAX actions, and apply proper input sanitization and output encoding to prevent Stored XSS. Update to the patched version when available.

Recommended fix Moderate confidence

Upgrade to My Marginalia version 1.0.7 or later

  1. 1. Back up your WordPress site database and files
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate the 'My Marginalia' plugin in the list
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Alternatively, download the latest version from the WordPress Plugin Repository and upload it manually
  6. 6. Verify the plugin is updated to version 1.0.7 or later
  7. 7. Test that the plugin functionality still works as expected
Caveat None expected - this is a security patch update

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-39435 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-39435 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data