Automated Threat Modeling

TextBuilder WordPress Plugin CVE-2025-9213: Brief Summary of a High-Severity CSRF Vulnerability

A brief summary of CVE-2025-9213, a critical Cross-Site Request Forgery vulnerability in the TextBuilder WordPress plugin (versions 1.0.0 to 1.1.1). It covers the technical mechanism, the affected versions, and vendor context from public sources. It includes no patch or detection guidance, because none is currently available.

CVE Analysis

7 min read

ZeroPath CVE Analysis
ZeroPath CVE Analysis

2025-10-03

TextBuilder WordPress Plugin CVE-2025-9213: Brief Summary of a High-Severity CSRF Vulnerability
Experimental AI-Generated Content

This CVE analysis is an experimental publication that is completely AI-generated. The content may contain errors or inaccuracies and is subject to change as more information becomes available. We are continuously refining our process.

If you have feedback, questions, or notice any errors, please reach out to us.

[email protected]

Introduction

Attackers can take over WordPress administrator accounts by exploiting a flaw in the TextBuilder plugin's authentication workflow. If an administrator is tricked into clicking a malicious link or visiting a crafted page, the attacker can make unauthorized changes to that user's credentials. The effect is immediate, and the attacker needs no authentication of their own to change the account's password and email address.

TextBuilder is an AI-powered content creation plugin for WordPress, developed by TextBuilder.ai. It has over 5,000 active installations and is widely used by site owners who want automated content. The plugin integrates with external AI services and was adopted rapidly after its release.

Technical Information

CVE-2025-9213 is a Cross-Site Request Forgery vulnerability in the TextBuilder WordPress plugin, versions 1.0.0 through 1.1.1. The root cause is missing or incorrect nonce validation in the handleToken function. WordPress nonces are meant to ensure that only legitimate users can perform sensitive actions: each request must include a unique token, and that token is verified. TextBuilder either omits this validation or implements it incorrectly, so the endpoint is open to CSRF attacks.

An attacker can craft a malicious request to the vulnerable endpoint and use social engineering to deliver it to a logged-in administrator. If the administrator interacts with the malicious content while authenticated, the request is processed with the administrator's privileges. The attacker does not need to be authenticated. Once the forged request is accepted, the attacker-supplied authorization token is set for the targeted user. That token allows later changes to the user's password and email address, which amounts to a full account takeover.

No public code for the vulnerable function has been released. Every plugin installation running versions 1.0.0 through 1.1.1 is vulnerable.

Affected Systems and Versions

  • Product: TextBuilder WordPress plugin
  • Affected versions: 1.0.0, 1.1.0, 1.1.1
  • All configurations of these versions are vulnerable

Vendor Security History

No public vulnerabilities in TextBuilder.ai's plugin had been reported in the WordPress plugin repository before this one. As of September 30, 2025, the plugin was closed pending a full security review. The rapid release cycle and the integration with external AI services may have contributed to the nonce validation oversight. There is no public record of earlier security advisories or patch response metrics for this vendor.

References

Detect & fix
what others miss

Works with
  • GitHub
  • GitLab
  • Bitbucket
  • Azure DevOps Services
  • Gerrit
  • CVS
  • Jira
  • Linear
  • Slack
  • Security Compass
Explore integrations
Security magnifying glass visualization