CVE-2026-4133: CWE-352 Cross-Site Request Forgery (CSRF) in textp2p TextP2P Texting Widget
The TextP2P Texting Widget plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to and including 1.7. 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.
AI Analysis
Technical Summary
The TextP2P Texting Widget plugin for WordPress suffers from a CSRF vulnerability due to the absence of nonce validation in the imTextP2POptionPage() function. Specifically, the form responsible for settings updates lacks a wp_nonce_field(), and the POST request handler does not verify the nonce using check_admin_referer() or wp_verify_nonce(). This allows unauthenticated attackers to submit forged requests that modify all plugin settings if an administrator is tricked into performing an action such as clicking a crafted link. The vulnerability affects all versions up to and including 1.7.
Potential Impact
An attacker can cause a site administrator to unknowingly submit a request that changes plugin settings, including sensitive configurations like API credentials and reCAPTCHA settings. This could lead to unauthorized control over the plugin's behavior and potentially weaken site security or functionality. There is no direct confidentiality or availability impact indicated, but integrity of plugin settings is compromised.
Mitigation Recommendations
Patch status is not yet confirmed — no official fix or patch links are provided. Users should monitor the vendor's advisory for updates. Until a patch is available, administrators should avoid clicking untrusted links while logged into WordPress admin and consider restricting access to the plugin settings page. Implementing manual nonce validation or other CSRF protections in the plugin code could mitigate the risk.
CVE-2026-4133: CWE-352 Cross-Site Request Forgery (CSRF) in textp2p TextP2P Texting Widget
Description
The TextP2P Texting Widget plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to and including 1.7. 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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The TextP2P Texting Widget plugin for WordPress suffers from a CSRF vulnerability due to the absence of nonce validation in the imTextP2POptionPage() function. Specifically, the form responsible for settings updates lacks a wp_nonce_field(), and the POST request handler does not verify the nonce using check_admin_referer() or wp_verify_nonce(). This allows unauthenticated attackers to submit forged requests that modify all plugin settings if an administrator is tricked into performing an action such as clicking a crafted link. The vulnerability affects all versions up to and including 1.7.
Potential Impact
An attacker can cause a site administrator to unknowingly submit a request that changes plugin settings, including sensitive configurations like API credentials and reCAPTCHA settings. This could lead to unauthorized control over the plugin's behavior and potentially weaken site security or functionality. There is no direct confidentiality or availability impact indicated, but integrity of plugin settings is compromised.
Mitigation Recommendations
Patch status is not yet confirmed — no official fix or patch links are provided. Users should monitor the vendor's advisory for updates. Until a patch is available, administrators should avoid clicking untrusted links while logged into WordPress admin and consider restricting access to the plugin settings page. Implementing manual nonce validation or other CSRF protections in the plugin code could mitigate the risk.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-03-13T14:22:05.633Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69e8877019fe3cd2cd808fe0
Added to database: 4/22/2026, 8:31:44 AM
Last enriched: 4/22/2026, 8:48:13 AM
Last updated: 4/23/2026, 2:38:20 AM
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.