CVE-2026-118801: aBlocks <= 2.18.0 - Authenticated (Contributor+) Sensitive Information Exposure in 'ablocks_template' Shortcode

Q: Who can exploit this issue?

Any authenticated user with at least the Contributor role can exploit it to retrieve the fully rendered body content of password-protected posts, using a target post ID. Authors and higher-privileged users can also publish content containing the shortcode.

Q: Can this expose protected content to visitors who are not logged in?

Yes. An attacker with Author-level access or higher can publish a post that embeds the shortcode with the ID of a password-protected post, making that rendered content available to unauthenticated visitors.

Q: What content is at risk?

The issue affects the full rendered body content of any password-protected post, regardless of post type. The attacker needs the ID of the target post and authenticated Contributor-level access or above.

Published Nov 7, 2026

Updated

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.

Event History

Nov 7, 2026

CVE Published

via MITRE·06:39 AM

Data Sourced

via MITRE·06:39 AM

DescriptionSeverityWeakness

Data Sourced

via NVD·07:17 AM

DescriptionSeverityWeakness

Frequently Asked Questions

Who can exploit this issue?

Any authenticated user with at least the Contributor role can exploit it to retrieve the fully rendered body content of password-protected posts, using a target post ID. Authors and higher-privileged users can also publish content containing the shortcode.

Can this expose protected content to visitors who are not logged in?

Yes. An attacker with Author-level access or higher can publish a post that embeds the shortcode with the ID of a password-protected post, making that rendered content available to unauthenticated visitors.

What content is at risk?

The issue affects the full rendered body content of any password-protected post, regardless of post type. The attacker needs the ID of the target post and authenticated Contributor-level access or above.

CVE-2026-118801: aBlocks <= 2.18.0 - Authenticated (Contributor+) Sensitive Information Exposure in 'ablocks_template' Shortcode

Event History

Frequently Asked Questions

Who can exploit this issue?

Can this expose protected content to visitors who are not logged in?

What content is at risk?

Company

Resources

Contact

Frequently Asked Questions

Who can exploit this issue?

Can this expose protected content to visitors who are not logged in?

What content is at risk?