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

CVE-2025-31404

HIGH · 7.1 CVSS v3.1 Published 2025-04-09
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 Wladyslaw Madejczyk AF Tell a Friend af-tell-a-friend allows Stored XSS.This issue affects AF Tell a Friend: from n/a through <= 1.4.

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

Cross-Site Request Forgery (CSRF) vulnerability in the AF Tell a Friend WordPress plugin (versions through 1.4) allows attackers to inject malicious scripts via stored XSS. The lack of anti-CSRF tokens on forms enables attackers to craft malicious requests that trick authenticated administrators into executing unintended actions, leading to persistent script injection.

MitigationImplement WordPress nonces and CSRF tokens on all forms, and apply proper input sanitization plus output encoding to prevent stored XSS.

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. Verify AF Tell a Friend plugin is installed
    Navigate to WordPress admin > Plugins and look for 'AF Tell a Friend' in the installed plugins list, or query the database wp_plugins table for the plugin slug
    Affected if The plugin is installed and active on the WordPress site
  2. Check the installed plugin version
    In WordPress admin > Plugins, find AF Tell a Friend and view the version number displayed, or inspect the plugin main file header for the Version tag
    Affected if The version is 1.4 or lower (all versions through 1.4 are affected)
  3. Inspect plugin forms for CSRF protection
    Examine the PHP source code of the plugin, specifically the form handling functions, and look for wp_nonce_field() or check_admin_referer() calls on any form that accepts user input
    Affected if The forms lack nonce verification or token validation logic
  4. Check for stored XSS vulnerabilities in input handling
    Review the plugin code for how user-submitted data (particularly the 'tell a friend' message fields) is handled - look for lack of sanitization functions like esc_html(), esc_attr(), or sanitize_text_field() before output
    Affected if User input is stored and displayed without proper sanitization and output encoding

If the AF Tell a Friend plugin version 1.4 or lower is installed and its forms lack nonce/CSRF token validation with unsanitized input storage, the environment is affected by this CVE.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement WordPress nonces and CSRF tokens on all forms, and apply proper input sanitization plus output encoding to prevent stored XSS.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-31404 — 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-31404 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