Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-14283: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in wpblockart BlockArt Blocks – Gutenberg Blocks, Page Builder Blocks ,WordPress Block Plugin, Sections & Template Library

0
Medium
VulnerabilityCVE-2025-14283cvecve-2025-14283cwe-79
Published: Wed Jan 28 2026 (01/28/2026, 11:23:40 UTC)
Source: CVE Database V5
Vendor/Project: wpblockart
Product: BlockArt Blocks – Gutenberg Blocks, Page Builder Blocks ,WordPress Block Plugin, Sections & Template Library

Description

The BlockArt Blocks – Gutenberg Blocks, Page Builder Blocks ,WordPress Block Plugin, Sections & Template Library plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the BlockArt Counter in all versions up to, and including, 2.2.14 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/27/2026, 11:03:28 UTC

Technical Analysis

CVE-2025-14283 is a stored cross-site scripting vulnerability classified under CWE-79, found in the BlockArt Blocks – Gutenberg Blocks, Page Builder Blocks, WordPress Block Plugin, Sections & Template Library plugin. This vulnerability affects all versions up to and including 2.2.14. The root cause is insufficient sanitization and escaping of user-supplied input in the BlockArt Counter component, which is used to display counters on pages. Authenticated users with contributor-level permissions or higher can inject arbitrary JavaScript code into pages via crafted input fields. Because the malicious script is stored persistently, it executes every time any user accesses the infected page, potentially compromising session tokens, cookies, or enabling further attacks such as privilege escalation or defacement. The CVSS 3.1 base score is 6.4, reflecting a medium severity level, with attack vector network-based, low attack complexity, requiring privileges (authenticated contributor), no user interaction, and scope change due to impact on other users. No patches or official fixes are currently linked, and no known exploits have been reported in the wild. The vulnerability is significant for WordPress sites using this plugin, especially those with multiple contributors and public-facing content.

Potential Impact

The impact of CVE-2025-14283 is primarily on the confidentiality and integrity of affected WordPress sites. An attacker with contributor-level access can inject malicious scripts that execute in the browsers of site visitors and administrators, potentially stealing session cookies, performing actions on behalf of users, or defacing content. This can lead to unauthorized access, data leakage, or reputational damage. Since the vulnerability does not affect availability directly, denial-of-service impact is low. However, the scope is broad because the injected script affects all users viewing the compromised page, including administrators. Organizations with multiple contributors and public-facing WordPress sites are at higher risk. The requirement for authenticated access limits exploitation to insiders or compromised accounts, but the ease of exploitation is low complexity. The lack of known exploits in the wild currently reduces immediate risk but does not preclude future attacks.

Mitigation Recommendations

To mitigate CVE-2025-14283, organizations should first check for updates or patches from the plugin vendor and apply them promptly once available. In the absence of official patches, administrators should restrict contributor-level permissions to trusted users only and audit existing content for suspicious scripts or injected code. Implementing a Web Application Firewall (WAF) with rules to detect and block XSS payloads targeting the BlockArt Counter fields can reduce risk. Additionally, site owners can temporarily disable or remove the vulnerable BlockArt Counter feature or the entire BlockArt Blocks plugin if feasible. Employing Content Security Policy (CSP) headers to restrict script execution sources can also mitigate the impact of injected scripts. Regular security reviews and monitoring for unusual activity or content changes are recommended. Finally, educating contributors about safe input practices and monitoring user roles can help prevent exploitation.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-12-08T18:30:39.600Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6979f49d4623b1157cb36500

Added to database: 1/28/2026, 11:35:57 AM

Last enriched: 2/27/2026, 11:03:28 AM

Last updated: 3/24/2026, 10:25:26 AM

Views: 31

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses