EUVD-2026-24677
GHSA-8qm3-xq92-849m
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Lifecycle Timeline
4DescriptionCVE.org
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.
AnalysisAI
Cross-site request forgery in TextP2P Texting Widget plugin for WordPress up to version 1.7 allows unauthenticated attackers to modify all plugin settings including API credentials and widget configuration by tricking site administrators into clicking a malicious link. The vulnerability stems from missing nonce validation in the settings update handler, enabling attackers to change chat titles, messages, colors, reCAPTCHA configuration, and other sensitive options without authentication or authorization verification. This requires user interaction (admin must click attacker-controlled link) but affects any WordPress site running the vulnerable plugin with an active administrator.
Technical ContextAI
The TextP2P Texting Widget plugin for WordPress fails to implement CSRF protection mechanisms (CWE-352: Cross-Site Request Forgery) in its settings administration page. Specifically, the imTextP2POptionPage() function processes POST requests to update plugin configuration at line 7 without calling wp_verify_nonce() or check_admin_referer(), and the corresponding HTML form at line 314 lacks a wp_nonce_field() output. WordPress nonces are cryptographic tokens tied to user sessions and actions that prevent unauthorized form submissions from third-party sites. The absence of nonce generation and validation allows any attacker to craft a form or JavaScript that, when submitted by a logged-in administrator, will process unvalidated settings changes as if authorized by the administrator. This affects all versions up to and including 1.7 of the plugin (CPE: cpe:2.3:a:textp2p:textp2p_texting_widget:*:*:*:*:*:*:*:*), indicating no version-specific restrictions on the vulnerable code path.
RemediationAI
Sites running TextP2P Texting Widget should update to the latest available version immediately, as patched versions should include wp_nonce_field() in the settings form HTML and wp_verify_nonce() or check_admin_referer() calls in the POST handler. Consult the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/2d36fa25-108b-462b-b84e-2e77943b1871) and WordPress plugin repository for the specific patched version number. If an update is not yet released, disable the TextP2P Texting Widget plugin entirely via WordPress admin or deactivate it through a hosting control panel to prevent exploitation; note that this removes the chat widget functionality until patching is available. As a temporary mitigation, restrict access to the WordPress admin interface (/wp-admin/) using network-level controls (IP allowlisting, .htaccess rules, or firewall rules) to limit which machines can reach the settings page, reducing the likelihood that an attacker can trick an administrator into clicking a malicious link from an external network; however, this is cumbersome for distributed teams and does not eliminate the risk from internal phishing. Additionally, enforce the use of security plugins (e.g., Wordfence) that can log and alert on unexpected settings changes, providing post-exploitation detection if nonce validation cannot be enforced.
The isMail transport in PHPMailer before 5.2.20 might allow remote attackers to pass extra parameters to the mail comman
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Country State City Dropdown CF7 plugin for WordPress is vulnerable to SQL Injection via the ‘cnt’ and 'sid' paramete
Same weakness CWE-352 – Cross-Site Request Forgery (CSRF)
View allShare
External POC / Exploit Code
Leaving vuln.today