CVE-2026-4133 MEDIUM

CVE-2026-4133: TextP2P Texting Widget <= 1.7 - Cross-Site Request Forgery to Settings Update

Vendor Textp2P
Product TextP2P Texting Widget
Weakness CWE-352 · CSRF
Published April 22, 2026
Last update April 23, 2026

CVSS base score

4.3/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction Required
Confidentiality None
Integrity Low

CVSS vector

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

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

TextP2P Texting Widget versions 1.7 and earlier are vulnerable to cross-site request forgery (CSRF) attacks. An attacker can craft a malicious webpage that, when visited by a logged-in site administrator, performs unwanted actions within the widget without the admin's knowledge or consent. The attack requires the victim to visit the attacker's page while authenticated to the site.

What an attacker can do

03Attacker Capabilities

Perform unwanted actions on behalf of a logged-in administrator without their knowledge.

Potential impact on your site

04Site Impact

An attacker can trick administrators into unknowingly modifying widget settings or performing other administrative actions.

Conditions required to exploit

05Prerequisites

The site administrator must visit a malicious webpage while logged into the site.

Key dates

06Disclosure timeline

April 22, 2026 CVE published
April 23, 2026 Record updated

Related vulnerabilities

08Related CVE