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

CVE-2025-31440

HIGH · 7.1 CVSS v3.1 Published 2025-03-28
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 Strategy11 Team Terms of Use terms-of-use-2 allows Stored XSS.This issue affects Terms of Use: from n/a through <= 2.0.

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 Strategy11 Team Terms of Use plugin (terms-of-use-2) allows attackers to trick authenticated administrators into submitting malicious requests that store XSS payloads. The lack of proper CSRF token validation enables attackers to craft malicious forms or links that, when clicked by a logged-in admin, inject and persist malicious scripts into the plugin's settings.

MitigationImplement WordPress nonces for all form submissions and AJAX actions to prevent CSRF attacks, and ensure all user-supplied data is properly sanitized before storage and escaped when output 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. Confirm the Team Terms of Use plugin is installed
    Navigate to WordPress Admin > Plugins and look for 'Team Terms of Use' or 'terms-of-use-2' in the installed plugins list; alternatively, check the /wp-content/plugins/ directory for a folder named 'terms-of-use-2'
    Affected if The plugin is present and active in the WordPress installation
  2. Identify the installed plugin version
    In the WordPress plugin admin page, click on the plugin name to view its details, or inspect the main plugin file (e.g., terms-of-use-2.php) and look for a 'Version:' comment in the file header
    Affected if The installed version has not been patched for CSRF protection (no version range was specified, so compare your version to any release notes or security advisories from Strategy11)
  3. Verify administrator accounts exist
    Go to WordPress Admin > Users and confirm there is at least one user with the 'Administrator' role
    Affected if Any administrator accounts exist, as they are the target of this CSRF attack vector
  4. Inspect plugin settings pages for CSRF protection
    Access the plugin's settings page (usually under 'Team' or 'Terms of Use' in the admin menu); view the page source (right-click > View Page Source) and search for 'wp_nonce' or '_wpnonce' fields in any forms
    Affected if Forms on the plugin settings pages lack nonce fields, indicating missing CSRF protection

Your environment is affected if the Team Terms of Use plugin (terms-of-use-2) is installed, active, and its admin forms lack WordPress nonce verification, allowing administrators to be targeted via CSRF for stored XSS injection.

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 WordPress nonces for all form submissions and AJAX actions to prevent CSRF attacks, and ensure all user-supplied data is properly sanitized before storage and escaped when output to prevent stored XSS.

Recommended fix Moderate confidence

Latest version of Team Terms of Use plugin (version higher than 2.0)

  1. Check the current version of the Team Terms of Use plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate 'Team Terms of Use' by Strategy11 and note the current version
  4. If the installed version is <= 2.0, update the plugin to the latest available version from the WordPress plugin repository
  5. After updating, verify the plugin is functioning correctly and review any admin settings that may have been affected

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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