TextP2P Texting Widget <= 1.8 - Cross-Site Request Forgery to Settings Update
Strategic Overview
- Status
- Patched in 1.9
- Affected Plugin
- TextP2P Texting Widget
- Affected Version
<= 1.8- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2026-4133
At a glance
CVE-2026-4133 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the TextP2P Texting Widget WordPress plugin, affecting versions <= 1.8. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.9; sites on affected versions should update now. Disclosed April 2026, reported by afnaan.
Vulnerability Overview
The TextP2P Texting Widget plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to and including 1.8. This is due to missing nonce validation in the imTextP2POptionPage() function which processes settings updates. The form at line 314 does not include a wp_nonce_field(), and the POST handler at line 7 does not call check_admin_referer() or wp_verify_nonce() before processing settings changes. This makes it possible for unauthenticated attackers to update all plugin settings including chat widget titles, messages, API credentials, colors, and reCAPTCHA configuration via a forged request, granted they can trick a site administrator into performing an action such as clicking a link.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
TextP2P Texting Widget <= 1.8 carries this weakness at imTextP2POptionPage(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For TextP2P Texting Widget the fix is 1.9: builds <= 1.8 are affected, anything from 1.9 onward is not.
Remediation
Update to version 1.9, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to TextP2P Texting Widget: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: TextP2P Texting Widget 1.9 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C