CVE-2026-11900
Received Received - Intake

Insecure Direct Object Reference in Ad Inserter WordPress Plugin

Vulnerability report for CVE-2026-11900, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-03

Last updated on: 2026-07-03

Assigner: Wordfence

Description

The Ad Inserter – Ad Manager & AdSense Ads plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to and including 2.8.16 via the 'data' attribute of the [adinserter] shortcode. This is due to the replace_ai_tags() function processing a {reusable-block-N} tag pattern that calls get_post_field('post_content', N) without verifying the requesting user's capability with current_user_can('read_post'), without restricting the post type to 'wp_block', and without checking the post status. This makes it possible for authenticated attackers, with Contributor-level access and above, to read the full content of arbitrary posts including Private, Draft, Pending, Trashed, and password-protected posts owned by other users, by placing the shortcode in a post they own and previewing it.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-03
Last Modified
2026-07-03
Generated
2026-07-03
AI Q&A
2026-07-03
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
advanced_ads ad_inserter to 2.8.16 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

The Ad Inserter – Ad Manager & AdSense Ads plugin for WordPress has an Insecure Direct Object Reference vulnerability in versions up to and including 2.8.16. This occurs via the 'data' attribute of the [adinserter] shortcode. The vulnerability arises because the replace_ai_tags() function processes a {reusable-block-N} tag pattern that calls get_post_field('post_content', N) without verifying if the requesting user has permission to read the post, without restricting the post type to 'wp_block', and without checking the post status.

As a result, authenticated users with Contributor-level access or higher can read the full content of arbitrary posts, including Private, Draft, Pending, Trashed, and password-protected posts owned by other users, by placing the shortcode in a post they own and previewing it.

Impact Analysis

This vulnerability allows attackers with Contributor-level access or above to read the full content of arbitrary posts they should not have access to. This includes Private, Draft, Pending, Trashed, and password-protected posts owned by other users.

The impact is an unauthorized disclosure of potentially sensitive or confidential content within the WordPress site, which could lead to information leakage and privacy violations.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-11900. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart