CVE-2024-13465 MEDIUM

CVE-2024-13465: aBlocks – WordPress Gutenberg Blocks <= 1.6.1 - Authenticated (Contributor+) Stored Cross-Site Scripting

Vendor Kodezen
Product aBlocks – Gutenberg Blocks, User Dashboard Builder, Popup Builder, Form Builder & Animation Builder
Weakness CWE-79 · XSS
Published February 18, 2025
Last update April 8, 2026

CVSS base score

6.4/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality Low
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

What the vulnerability does

01Description

The aBlocks – WordPress Gutenberg Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the "Table Of Content" Block, specifically in the "markerView" attribute, in all versions up to, and including, 1.6.1 due to insufficient input sanitization and output escaping. 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.

Explanation of Vulnerability in Simple Terms

02Summary

aBlocks versions up to 1.6.1 contain a stored cross-site scripting (XSS) vulnerability that allows authenticated users to inject malicious scripts. These scripts execute in the browsers of other site visitors, potentially compromising their sessions or stealing sensitive data. The vulnerability affects the plugin's block, dashboard, popup, form, and animation builder components.

What an attacker can do

03Attacker Capabilities

Inject malicious scripts that execute in other users' browsers and steal their session data or credentials.

Potential impact on your site

04Site Impact

Compromised user accounts, stolen admin sessions, and malware distribution to site visitors if an attacker gains plugin access.

Conditions required to exploit

05Prerequisites

Attacker must have a WordPress user account with at least Contributor or Editor permissions to create or edit content.

Key dates

06Disclosure timeline

February 18, 2025 CVE published
April 8, 2026 Record updated

Related vulnerabilities

08Related CVE