CSRF in Textbuilder
CVE-2025-9213
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.
Vulnerability class: CSRF (Cross-Site Request Forgery)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 8.8 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.
EPSS exploit prediction
EPSS: 0.002 (6.9th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 7th percentile — 6.9% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.002 · newest: 0.002 · change: 0.000
Affected products
- Textbuilder — versions 1.0.0
Weakness classification (CWE)
References
Frequently asked questions
- What is CVE-2025-9213?
- CVE-2025-9213 is a high-severity vulnerability in Textbuilder, classified under Cross-Site Request Forgery (CSRF). CVSS score: 8.8/10. Published 2025-10-03.
- How severe is CVE-2025-9213?
- High severity. CVSS v3 base score is 8.8 out of 10.