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

CVE-2025-9213

HIGH · 8.8 CVSS v3.1 Published 2025-10-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
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
The TextBuilder plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions 1.0.0 to 1.1.1. This is due to missing or incorrect nonce validation on the 'handleToken' function. This makes it possible for unauthenticated attackers to update a user's authorization token via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. Once the token is updated, an attacker can update the user's password and email address.

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 · high confidence

The TextBuilder WordPress plugin versions 1.0.0 to 1.1.1 lacks proper nonce validation in its handleToken function, enabling CSRF attacks. Unauthenticated attackers can forge administrative requests to update a user's authorization token, then change the user's password and email to achieve full account takeover.

MitigationUpdate TextBuilder plugin to version 1.1.2 or later which includes proper nonce validation; alternatively disable the plugin until patched.

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Locate TextBuilder plugin installation
    In WordPress admin, go to Plugins > Installed Plugins and look for 'TextBuilder'. Alternatively, check the /wp-content/plugins/ directory for a textbuilder folder.
    Affected if TextBuilder plugin folder exists in the WordPress plugins directory
  2. Identify installed TextBuilder version
    In WordPress admin Plugins list, find TextBuilder and note the version number displayed under the plugin name. Or inspect /wp-content/plugins/textbuilder/readme.txt for the Version: field.
    Affected if Version is 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, 1.0.9, 1.1.0, or 1.1.1 (any version from 1.0.0 through 1.1.1)
  3. Confirm plugin is active
    In WordPress admin Plugins list, check if TextBuilder shows as 'Active' under the plugin status.
    Affected if Plugin is active and the version falls within the affected range
  4. Check for unauthorized token modifications
    Review WordPress user records in wp_users table for unexpected authorization_token meta values. Also check server access logs for POST requests to /wp-admin/admin-ajax.php with action=handleToken or similar token-related endpoints.
    Affected if Unexpected authorization_token values exist in user meta, or suspicious POST requests to token-handling endpoints appear in logs

User is affected if TextBuilder plugin version 1.0.0 through 1.1.1 is installed and active, exposing the handleToken function to CSRF exploitation.

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

Update TextBuilder plugin to version 1.1.2 or later which includes proper nonce validation; alternatively disable the plugin until patched.

Recommended fix Moderate confidence

Latest version after 1.1.1 (check WordPress plugin repository for 1.1.2 or higher)

  1. Check the current version of the TextBuilder plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate TextBuilder and verify the current version number
  4. If version is 1.1.1 or below, navigate to Plugins > Add New > Upload Plugin or check for an update
  5. Update to the latest available version of TextBuilder which includes the security fix for CVE-2025-9213
  6. After updating, verify the new version number in the plugins list
  7. Consider reviewing user accounts that may have been affected and reset passwords as a precaution

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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