CVE-2026-1093 MEDIUM

CVE-2026-1093: WPFAQBlock– FAQ & Accordion Plugin For Gutenberg <= 1.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'class' Shortcode Attribute

Vendor Creativewerkdesigns
Product WPFAQBlock– FAQ & Accordion Plugin For Gutenberg
Weakness CWE-79 · XSS
Published March 21, 2026
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 WPFAQBlock– FAQ & Accordion Plugin For Gutenberg plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'class' parameter of the 'wpfaqblock' shortcode in all versions up to, and including, 1.1 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.

Explanation of Vulnerability in Simple Terms

02Summary

WPFAQBlock versions 1.1 and earlier contain a cross-site scripting vulnerability that allows authenticated users to inject malicious scripts. The vulnerability affects the plugin's handling of user input in FAQ and accordion blocks. An attacker with low-level site access can craft malicious content that executes in other users' browsers, potentially compromising site security and user data.

What an attacker can do

03Attacker Capabilities

Inject JavaScript code that runs in other users' browsers when they view affected pages.

Potential impact on your site

04Site Impact

Authenticated attackers can steal admin session tokens, modify site content, or redirect users to malicious sites.

Conditions required to exploit

05Prerequisites

Attacker must have a low-privilege account (e.g., contributor or subscriber) on the WordPress site.

Key dates

06Disclosure timeline

March 21, 2026 CVE published
April 8, 2026 Record updated

Related vulnerabilities

08Related CVE