Ad Inserter EUVD-2026-41520

Exploitation requires an authenticated WordPress session with at minimum Contributor-level role, which grants the ability to create posts and use the post preview feature. The Ad Inserter plugin must be installed and active in a version up to and including 2.8.16. The attacker must be able to place the [adinserter] shortcode containing a {reusable-block-N} pattern in a post and trigger a preview render - both capabilities are available by default to Contributors. The numeric post ID of the target (N) must be known or enumerable; WordPress post IDs are sequential and trivially guessed by incrementing integers. Exploitation is bounded to reading post content fields and does not enable write operations, code execution, or privilege escalation. Sites where no untrusted users hold Contributor or higher roles have no exploitable attack surface. The vulnerability does not affect post metadata, user credentials, or configuration settings - only the post_content field of the target post.

The CVSS 4.3 score (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) accurately characterizes the real-world risk profile. The network vector and low attack complexity mean exploitation does not require special network positioning - any internet-accessible WordPress admin panel suffices. However, the PR:L metric confirms authenticated access at Contributor level is a hard prerequisite, meaningfully gating opportunistic mass exploitation. The confidentiality impact is partial (C:L), bounded to post content; there is no integrity or availability impact. The vulnerability is absent from the CISA KEV catalog and no public proof-of-concept exploit code has been identified, suggesting it has not attracted widespread exploitation tooling. EPSS data was not provided in the input, so exploitation probability cannot be quantified from that signal. In practice, risk scales directly with site architecture: a single-admin WordPress site has zero exposure, while a multi-author publishing platform, news site, or membership platform with active Contributor accounts and sensitive unpublished content faces real disclosure risk. The attack is trivial in technique - no exploit sophistication is required - so the Contributor access requirement is the primary barrier, not technical complexity.

An attacker with a Contributor-level WordPress account creates a new post containing the shortcode [adinserter data="{reusable-block-N}"] where N is any post ID on the site - IDs are sequential integers easily enumerated by incrementing from 1. By using the WordPress post preview feature, the shortcode is rendered server-side, and replace_ai_tags() fetches and returns the full content of the target post regardless of its Private, Draft, or password-protected status. No public proof-of-concept code exists, but the technique requires no special tooling beyond a browser and knowledge of the shortcode syntax.