PostX - Gutenberg Blocks for Post Grid <= 2.4.9 - Authenticated (Contributor+) Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 2.4.10
- Affected Plugin
- Post Grid Gutenberg Blocks – PostX
- Affected Version
< 2.4.10- CVSS
- 5.4Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2021-24659
At a glance
CVE-2021-24659 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Post Grid Gutenberg Blocks WordPress plugin, affecting versions < 2.4.10. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 2.4.10; sites on affected versions should update now. Disclosed August 2021, reported by apple502j.
Vulnerability Overview
The PostX – Gutenberg Blocks for Post Grid WordPress plugin before 2.4.10 allows users with a role as low as Contributor to perform Stored Cross-Site Scripting attacks via the plugin's block.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in Post Grid Gutenberg Blocks < 2.4.10 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 Post Grid Gutenberg Blocks the fix is 2.4.10: builds < 2.4.10 are affected, anything from 2.4.10 onward is not.
Remediation
Update to version 2.4.10, 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: Post Grid Gutenberg Blocks 2.4.10 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
- 7.2CVE-2023-36385: PostX – Gutenberg Blocks for Post Grid <= 2.9.9 XSS
CVE-2023-36385 - 6.4CVE-2026-5158: PostX <= 5.0.13 Stored Cross-Site Scripting
CVE-2026-5158 - 6.4CVE-2026-15100: Post Grid Gutenberg Blocks <= 5.0.32 Stored XSS
CVE-2026-15100 - 6.4CVE-2026-13253: Post Grid Gutenberg Blocks for News Stored XSS
CVE-2026-13253
Other vulnerabilities in Post Grid Gutenberg Blocks – PostX
- 8.8CVE-2024-10728: PostX Arbitrary Plugin Installation/Activation
CVE-2024-10728 - 8.8CVE-2024-5326: Post Grid Gutenberg Blocks… Arbitrary Options Update
CVE-2024-5326 - 7.5CVE-2025-12980: Post Grid Gutenberg… Unauthenticated Info Exposure
CVE-2025-12980 - 7.2CVE-2026-1273: PostX <= 5.0.8 Server-Side Request Forgery
CVE-2026-1273 - 7.2CVE-2025-55707: PostX <= 4.1.35 Privilege Escalation
CVE-2025-55707 - 6.5CVE-2021-24652: PostX - Gutenberg Blocks… Unauthorized Access Controls
CVE-2021-24652 - 6.4CVE-2025-31096: PostX <= 4.1.25 Stored Cross-Site Scripting
CVE-2025-31096 - 6.4CVE-2024-53818: PostX <= 4.1.15 Stored Cross-Site Scripting
CVE-2024-53818
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C