Textp2P Texting Widget
Approved changes feed: RSS · Atom
cpe:2.3:a:textp2p:textp2p_texting_widget:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Textp2P (ee803667-3ad1-57a6-a707-e72af27980ec) |
|---|---|
| Product | Textp2P Texting Widget (432467c2-3402-5b5d-87b1-f7320f100e7a) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-4133 |
vulnerable | 2026-06-08 08:05:12.668336 |
TextP2P Texting Widget <= 1.7 - Cross-Site Request Forgery to Settings Update
MEDIUM (4.3)
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.
Published: 2026-04-22T07:45:33.274Z
Updated: 2026-04-23T13:43:28.246Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.