CVE-2026-118800 · Package
NO FIX YET
The aBlocks WordPress plugin does not sanitize the headingTag parameter, so a logged-in contributor can save a page that runs scripts. The script then executes in the browser of any visitor who opens that page, including administrators.
first public Nov 7, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running the aBlocks plugin up to and including version 2.18.0. Exploitation needs a contributor-level account or higher, so sites with no untrusted contributors are at lower risk. Sites that do not run the plugin can skip it.
Not affected if no-contributor-accounts, plugin-not-installed
Who cares ablocks, self-hosted, wordpress
2.18.0; versions up to and including 2.18.0 are affectedNo fix yet, per the sources.
The aBlocks – Gutenberg Blocks, User Dashboard Builder, Popup Builder, Form Builder & Animation Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'headingTag' parameter in all versions up to, and including, 2.18.0 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.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.