CVE-2026-1852 | WooBeWoo Product Pricing Table Plugin up to 1.1.0 on WordPress updateLabel cross-site request forgery (EUVD-2026-22911)

VDB-357712 · CVE-2026-1852 · EUVD-2026-22911 WOOBEWOO PRODUCT PRICING TABLE PLUGIN UP TO 1.1.0 ON WORDPRESS UPDATELABEL CROSS-SITE REQUEST FORGERY HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 5.1 $0-$5k 3.73 Summaryinfo A vulnerability described as problematic has been identified in WooBeWoo Product Pricing Table Plugin up to 1.1.0 on WordPress. This vulnerability affects the function updateLabel. Executing a manipulation can lead to cross-site request forgery. This vulnerability is tracked as CVE-2026-1852. The attack can be launched remotely. No exploit exists. Detailsinfo A vulnerability was found in WooBeWoo Product Pricing Table Plugin up to 1.1.0 on WordPress. It has been declared as problematic. This vulnerability affects the function updateLabel. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. The CWE definition for the vulnerability is CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. As an impact it is known to affect integrity. CVE summarizes: The Product Pricing Table by WooBeWoo plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.1.0. This is due to missing or incorrect nonce validation on the updateLabel() and remove() functions. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages or delete pricing tables via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. The weakness was disclosed by Muhammad Nur Ibnu Hubab. The advisory is shared for download at wordfence.com. This vulnerability was named CVE-2026-1852 since 02/03/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available. There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product. The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-22911). Productinfo Type WordPress Plugin Vendor WooBeWoo Name Product Pricing Table Plugin Version 1.0 1.1.0 CPE 2.3info 🔒 🔒 CPE 2.2info 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 5.2 VulDB Meta Temp Score: 5.1 VulDB Base Score: 4.3 VulDB Temp Score: 4.2 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 6.1 CNA Vector (Wordfence): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Cross-site request forgery CWE: CWE-352 / CWE-862 / CWE-863 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: no mitigation known Status: 🔍 0-Day Time: 🔒 Timelineinfo 02/03/2026 CVE reserved 04/15/2026 +70 days Advisory disclosed 04/15/2026 +0 days VulDB entry created 04/15/2026 +0 days VulDB entry last update Sourcesinfo Advisory: wordfence.com Researcher: Muhammad Nur Ibnu Hubab Status: Not defined CVE: CVE-2026-1852 (🔒) GCVE (CVE): GCVE-0-2026-1852 GCVE (VulDB): GCVE-100-357712 EUVD: 🔒 Entryinfo Created: 04/15/2026 14:02 Updated: 04/15/2026 14:17 Changes: 04/15/2026 14:02 (65), 04/15/2026 14:17 (1) Complete: 🔍 Cache ID: 99:125:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸