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

AILast updated: 01/28/2026, 11:52:42 UTC

Technical Analysis

CVE-2025-14283 is a stored Cross-Site Scripting (XSS) vulnerability identified in the BlockArt Blocks – Gutenberg Blocks, Page Builder Blocks, WordPress Block Plugin, Sections & Template Library plugin. This vulnerability arises from improper neutralization of input during web page generation (CWE-79). Specifically, the BlockArt Counter component fails to adequately sanitize and escape user-supplied attributes, allowing authenticated users with contributor-level permissions or higher to inject arbitrary JavaScript code into pages. When other users access these pages, the injected scripts execute in their browsers, potentially compromising session tokens, user credentials, or enabling further attacks such as privilege escalation or defacement. The vulnerability affects all versions up to and including 2.2.14. The CVSS 3.1 base score is 6.4, reflecting a medium severity with network attack vector, low attack complexity, requiring privileges but no user interaction, and impacting confidentiality and integrity with a scope change. No public exploits have been reported yet. The vulnerability was published on January 28, 2026, and is assigned by Wordfence. The lack of patch links suggests a fix is pending or not yet publicly available. This vulnerability is particularly concerning for WordPress sites that allow contributor-level users to add or edit content, as it enables persistent script injection that affects all visitors of the compromised pages.

Potential Impact

For European organizations, this vulnerability poses a significant risk to websites running the affected BlockArt Blocks plugin, especially those that permit contributor-level user roles. Exploitation can lead to session hijacking, theft of sensitive user data, unauthorized actions performed on behalf of users, and defacement of web content. This can damage organizational reputation, lead to data breaches under GDPR regulations, and potentially cause service disruptions. Since the vulnerability allows scope change, it can affect users beyond the initial contributor, including administrators and visitors, amplifying the impact. Organizations in sectors such as media, e-commerce, education, and government that rely heavily on WordPress for content management are particularly vulnerable. The absence of known exploits reduces immediate risk but does not eliminate the threat, as attackers may develop exploits once the vulnerability details are widely known.

Mitigation Recommendations

European organizations should prioritize the following mitigations: 1) Monitor the BlockArt Blocks plugin vendor announcements and update to the patched version immediately upon release. 2) Until a patch is available, restrict contributor-level permissions to trusted users only and audit existing contributors for suspicious activity. 3) Implement Web Application Firewall (WAF) rules to detect and block common XSS payloads targeting the BlockArt Counter attributes. 4) Employ Content Security Policy (CSP) headers to limit script execution sources and reduce the impact of injected scripts. 5) Conduct regular security audits and code reviews of custom blocks or plugins that interact with user input. 6) Educate content contributors about safe input practices and the risks of injecting untrusted content. 7) Consider disabling or replacing the vulnerable plugin with alternative solutions that follow secure coding practices. 8) Monitor logs for unusual activity or error messages related to the BlockArt Counter feature.

Need more detailed analysis?Upgrade to Pro Console

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: 1/28/2026, 11:52:42 AM

Last updated: 2/7/2026, 8:24:50 PM

Views: 13

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 in Console -> Billing for AI refresh and higher limits.

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

Latest Threats