GenerateBlocks <= 1.3.5 - Authenticated (Contributor+) Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 1.4.0
- Affected Plugin
- GenerateBlocks
- Affected Version
<= 1.3.5- CVSS
- 6.4Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2021-24751
At a glance
CVE-2021-24751 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the GenerateBlocks WordPress plugin, affecting versions <= 1.3.5. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 1.4.0; sites on affected versions should update now. Disclosed November 2021, reported by apple502j.
Vulnerability Overview
The GenerateBlocks WordPress plugin before 1.4.0 does not validate the generateblocks/container block's tagName attribute, which could allow users with a role as low as contributor to perform Cross-Site Scripting attacks.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in GenerateBlocks <= 1.3.5 takes an account at Contributor level or above. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For GenerateBlocks the fix is 1.4.0: builds <= 1.3.5 are affected, anything from 1.4.0 onward is not.
Remediation
Update to version 1.4.0, or a newer patched version
How does WordSec protect against this?
An attacker needs Contributor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: GenerateBlocks 1.4.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in GenerateBlocks
- 6.5CVE-2026-3454: GenerateBlocks IDOR
CVE-2026-3454 - 6.5CVE-2025-11879: GenerateBlocks Improper Authorization
CVE-2025-11879 - 4.3CVE-2026-48877: GenerateBlocks <= 2.1.0 Information Disclosure
CVE-2026-48877 - 4.3CVE-2025-12512: GenerateBlocks <= 2.1.2 Information Exposure
CVE-2025-12512 - 4.3CVE-2024-13546: GenerateBlocks <= 1.9.1 Sensitive Information Exposure
CVE-2024-13546 - 4.3CVE-2024-1452: GenerateBlocks <= 1.8.2 Sensitive Information Exposure
CVE-2024-1452
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C