CVE-2026-3498 | wpblockart BlockArt Blocks Plugin up to 2.2.15 on WordPress Block Attribute cross site scripting

VDB-356959 · CVE-2026-3498 · GCVE-0-2026-3498 WPBLOCKART BLOCKART BLOCKS PLUGIN UP TO 2.2.15 ON WORDPRESS BLOCK ATTRIBUTE CROSS SITE SCRIPTING HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 4.9 $0-$5k 0.21 Summaryinfo A vulnerability, which was classified as problematic, has been found in wpblockart BlockArt Blocks Plugin up to 2.2.15 on WordPress. This impacts an unknown function of the component Block Attribute Handler. This manipulation causes cross site scripting. The identification of this vulnerability is CVE-2026-3498. It is possible to initiate the attack remotely. There is no exploit available. Detailsinfo A vulnerability classified as problematic was found in wpblockart BlockArt Blocks Plugin up to 2.2.15 on WordPress. Affected by this vulnerability is an unknown functionality of the component Block Attribute Handler. The manipulation with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. As an impact it is known to affect integrity. The summary by CVE is: The BlockArt Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'clientId' block attribute in all versions up to, and including, 2.2.15. This is due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The weakness was shared by Athiwat Tiprasaharn and Itthidej Aramsri. It is possible to read the advisory at wordfence.com. This vulnerability is known as CVE-2026-3498 since 03/03/2026. The exploitation appears to be easy. The attack can be launched remotely. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1059.007 according to MITRE ATT&CK. There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product. Productinfo Type WordPress Plugin Vendor wpblockart Name BlockArt Blocks Plugin Version 2.2.0 2.2.1 2.2.2 2.2.3 2.2.4 2.2.5 2.2.6 2.2.7 2.2.8 2.2.9 2.2.10 2.2.11 2.2.12 2.2.13 2.2.14 2.2.15 CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 4.9 VulDB Meta Temp Score: 4.9 VulDB Base Score: 3.5 VulDB Temp Score: 3.4 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 6.4 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 scripting CWE: CWE-79 / CWE-94 / CWE-74 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 03/03/2026 CVE reserved 04/11/2026 +38 days Advisory disclosed 04/11/2026 +0 days VulDB entry created 04/11/2026 +0 days VulDB entry last update Sourcesinfo Advisory: wordfence.com Researcher: Athiwat Tiprasaharn, Itthidej Aramsri Status: Not defined CVE: CVE-2026-3498 (🔒) GCVE (CVE): GCVE-0-2026-3498 GCVE (VulDB): GCVE-100-356959 Entryinfo Created: 04/11/2026 04:11 Changes: 04/11/2026 04:11 (65) Complete: 🔍 Cache ID: 99:973:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸