Skip to main content

Ad Inserter EUVDEUVD-2026-98345

| CVE-2026-89097 MEDIUM
Information Exposure (CWE-200)
2026-10-13 Wordfence GHSA-r84v-5jjr-cxrx
4.3
CVSS 3.1 · Vendor: Wordfence
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain subscriber-level account
  2. Delivery
    Trigger ai_wp_footer_hook output
  3. Exploit
    Read exposed post meta and config
  4. Execution
    Extract API tokens and server internals
  5. Impact
    Pivot to connected services

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK

2 techniques across 2 tactics: Collection, Discovery

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires an authenticated session at subscriber level or above (CVSS PR:L) on a WordPress site running Ad Inserter - Ad Manager & AdSense Ads version 2.8.18 or earlier; disclosure occurs through the plugin's ai_wp_footer_hook code path against default configurations, with no user interaction and no special plugin feature toggle named in the description. The main limiting factor is the account requirement: sites that disable open user registration confine this to existing trusted users, whereas sites permitting self-service subscriber signup are exploitable by any registrant. Sensitivity of the leak scales with the environment - exposure of other plugins' API tokens only matters where such integrations exist.

Impact

This is a genuine but moderate-priority issue, not a top-tier emergency. The CVSS 3.1 base score is 4.3 (Medium) with vector AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N - network-reachable, low complexity, but requiring authentication (PR:L, subscriber-level) and limited to confidentiality-only impact. No EPSS score, CISA KEV listing, or public POC was provided in the input, so exploitation likelihood signals are absent rather than reassuring: no public exploit identified at time of analysis. The principal factor elevating real risk above the raw score is the breadth of exposed data described - not just version strings and server internal IP, but API tokens and underscore-prefixed protected post meta written by OTHER plugins, plus hardening constants and the plugin block matrix. That breadth means the vendor's C:L rating is arguably conservative; leaked third-party API tokens can enable lateral movement to external services, which looks closer to a serious confidentiality loss. The limiting factor is the authentication requirement: WordPress sites that freely allow subscriber self-registration are meaningfully exposed, while sites with registration disabled face a much smaller attack surface. Net: prioritize patching on multi-user/open-registration sites; treat as routine hygiene on single-admin sites.

Exploit ScenarioDerived

An attacker registers (or already holds) a low-privileged subscriber account on a WordPress site running Ad Inserter ≤2.8.18, then triggers the ai_wp_footer_hook output path to harvest the site's server internal IP, PHP/WordPress/theme versions, hardening constants, and all post meta - including protected underscore-prefixed keys containing API tokens from other plugins. The harvested tokens and configuration intelligence are then reused to pivot against connected third-party services or to tailor follow-on attacks. No public exploit code was identified in the provided data, and exploitation requires only an authenticated low-privilege session with no user interaction.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 13, 2026

Sensitive information exposure in the Ad Inserter - Ad Manager & AdSense Ads plugin for WordPress lets any authenticated user at subscriber level or above pull diagnostic and environment data out of the site through the plugin's ai_wp_footer_hook code path, affecting all releases up to and including 2.8.18. The leaked material spans the server's internal IP address, PHP configuration, WordPress and theme versions, hardening constants, the plugin's full block matrix, and every post meta value - including underscore-prefixed protected keys such as API tokens and private integration state written by other plugins. No public exploit code has been identified at time of analysis and the flaw is not confirmed actively exploited (CISA KEV); the main constraint is the account requirement, so sites that allow open subscriber self-registration have a materially larger exposure surface than sites that restrict registration to trusted users.

RemediationAI

No vendor-released patched version is independently confirmed in the available data; the plugin Trac changeset (https://plugins.trac.wordpress.org/changeset?reponame=&old=3709957%40ad-inserter&new=3709957%40ad-inserter) indicates an upstream fix has been committed, so treat the fix as upstream-fix-available pending confirmation of a tagged release and verify the current version on wordpress.org before upgrading past 2.8.18 - the safest interim action is to deactivate the plugin, which removes the ai_wp_footer_hook exposure entirely at the cost of losing ad-insertion functionality. If the plugin must remain active, close the account-requirement gap that makes this exploitable: disable open registration (WordPress Settings > General > Membership) and audit existing accounts so no untrusted subscriber-level users remain, accepting that this only reduces the population of potential abusers and does not fix the underlying disclosure. Because the leak includes all wp_postmeta values, assume any secrets held there for the site may have been read by any subscriber-level account created during the exposure window: rotate API tokens and integration credentials stored by other plugins, and review wp_postmeta for plaintext secrets to migrate into a properly protected store. As a lower-confidence compensating control, restrict network access to the site's front end for known accounts and monitor for subscriber-level sessions retrieving footer content at unusual rates, but note that these measures add operational friction and cannot substitute for the code fix. Additional guidance is available from the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/60ef9840-12c3-408a-b304-3eff2fe33bb4?source=cve.

Affected VersionsENISA

Ad Inserter – Ad Manager & AdSense Ads 0 ≤2.8.18

Affected Packages

euvd ad_inserter_ad_manager_adsense_ads no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

This is a CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) flaw in a WordPress plugin, rooted in a capability-check failure rather than a memory-safety or injection defect. WordPress plugins routinely emit footer markup via hooks such as wp_footer; Ad Inserter's ai_wp_footer_hook surfaces internal diagnostic state (server internal IP address, PHP configuration details, WordPress and theme version banners, hardening constants like file-edit and debug flags, the plugin's block matrix, and raw post meta) without restricting that output to users holding administrative capabilities. The referenced source lines in ad-inserter.php (tags/2.8.18, lines 4694, 4755, 4943 and 13304) mark the code paths where this data is assembled and returned. The distinguishing amplifier here is post meta enumeration: because WordPress stores third-party plugin integration state in wp_postmeta, the leak crosses plugin boundaries and can expose API tokens and credentials written by other plugins, meaning the blast radius depends on which integrations a given site has installed. The CPE cpe:2.3:a:spacetime:ad_inserter_-_ad_manager_&_adsense_ads:* confirms the vendor namespace (spacetime) and that the affected range is unconstrained by version in the CPE itself, matching the vendor statement of 'all versions up to and including 2.8.18'. Authentication requirements are confirmed from the CVSS vector (PR:L): exploitation requires a logged-in account at subscriber level or above, with network reachability (AV:N), low attack complexity (AC:L) and no user interaction (UI:N).

Know when PHP gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Wordfence) PRIMARY 4.3 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
vuln.today AI 6.5 MEDIUM

Subscriber auth gives PR:L; disclosure of other plugins' API tokens and protected meta is a serious confidentiality loss (C:H), with no integrity or availability impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

DescriptionCVE.org

The Ad Inserter - Ad Manager & AdSense Ads plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.8.18 via the ai_wp_footer_hook. This makes it possible for authenticated attackers, with subscriber-level access and above, to extract sensitive data including the server's internal IP address, PHP configuration, WordPress and theme versions, hardening constants, the plugin's full block matrix, and all post meta values including underscore-prefixed protected keys such as API tokens and private integration state written by other plugins.

Threat Intelligence Overview

EPSS Score
0.2%
Top 86% exploitable
Prevalence
High
Ad Inserter is a very widely deployed WordPress ad-management plugin
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
High

Priority Score

22
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +22
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

More in PHP

View all
CVE-2019-11043 CRITICAL POC
9.8 Oct 28

In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it

CVE-2012-1823 CRITICAL POC
9.8 May 11

sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not

CVE-2016-1555 CRITICAL POC
9.8 Apr 21

(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear

CVE-2018-11138 CRITICAL POC
9.8 May 31

The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by

CVE-2024-11680 CRITICAL POC
9.8 Nov 26

ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C

CVE-2025-49113 CRITICAL POC
9.9 Jun 02

Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au

CVE-2017-9841 CRITICAL POC
9.8 Jun 27

Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c

CVE-2025-0108 HIGH POC
8.8 Feb 12

Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers

CVE-2021-25298 HIGH POC
8.8 Feb 15

Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re

CVE-2021-25296 HIGH POC
8.8 Feb 15

Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re

CVE-2013-4983 CRITICAL POC
10.0 Sep 10

The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows

CVE-2023-6553 CRITICAL POC
9.8 Dec 15

The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy