CVE-2026-118801 · Package
NO FIX YET
The aBlocks WordPress plugin up to and including 2.18.0 lets a logged-in contributor embed a shortcode with another post's ID to read the full body of that post, even when it is password-protected. An author can publish such a post so unauthenticated visitors see the protected content.
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 2.18.0 that have password-protected posts and give contributor-level or higher accounts to users. Sites without the plugin, or without password-protected content, are not exposed through this flaw. The sources do not state a fixed version.
Not affected if no-password-protected-posts, plugin-not-installed
Who cares ablocks, self-hosted, wordpress
2.18.0 are affected.No fix yet, per the sources.
The aBlocks – Gutenberg Blocks, User Dashboard Builder, Popup Builder, Form Builder & Animation Builder plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.18.0 via the 'id' parameter. This makes it possible for authenticated attackers, with contributor-level access and above, to extract the full rendered body content of any password-protected post of any post type by embedding the shortcode with the target post's ID. Author-level attackers and above can additionally publish a post embedding the shortcode, exposing the password-protected content to unauthenticated visitors.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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.