Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft link with XSS payload in 's' parameter
-
DeliveryPhish logged-in victim to click
-
ExploitSearch page reflects unsanitized {title} placeholder
-
ExecutionScript executes in victim's session
-
ImpactHijack session or perform actions as victim
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that a site administrator has configured at least one Ad Inserter block using the {title} or {short-title} placeholder with that block enabled for search pages - a standard, documented feature but NOT a default configuration. Additionally, per CVSS UI:R, a victim must be tricked into clicking an attacker-crafted search URL (the 's' parameter carries the payload). The attack is unauthenticated (PR:N) from the attacker's side, but these two gates - the specific block/placeholder configuration AND required victim interaction - substantially limit realistic exploitation. Affects all versions of Ad Inserter - Ad Manager & AdSense Ads (vendor: spacetime) up to and including 2.8.18; fixed in 2.8.19. |
| Impact | This is a reflected Cross-Site Scripting flaw rated CVSS 6.1 (Medium) with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N. The signals are internally consistent: network-exploitable, low complexity, no privileges required, but it mandates user interaction (UI:R) - the victim must click a crafted link - which meaningfully caps real-world impact to session-scoped script execution (C:L/I:L, scope-changed S:C as the payload crosses into the victim's authenticated browser context). Crucially, exploitation is further gated by a non-default server-side precondition: a site admin must have configured an Ad Inserter block using the {title} or {short-title} placeholder AND enabled it for search pages. No EPSS score, KEV listing, or POC is provided, so exploitation status is: no public exploit identified at time of analysis. This is NOT a drop-everything priority - it is a classic reflected XSS requiring both social engineering and a specific (though documented and legitimate) plugin configuration. Its main risk amplifier is the plugin's very large install base, which raises the number of potentially-affected sites even though per-site exploitability depends on configuration. Treat as routine-patch priority. |
| Exploit ScenarioDerived | An attacker crafts a malicious URL targeting the vulnerable site's search page with a JavaScript payload in the 's' search parameter and lures a logged-in user (e.g. an administrator) into clicking it via phishing. If the site has an Ad Inserter block using the {title}/{short-title} placeholder enabled on search pages, the unsanitized search term is reflected and the script executes in the victim's browser session. No public POC is referenced, and exploitation requires user interaction. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 01, 2026
Reflected cross-site scripting (XSS) in the Ad Inserter - Ad Manager & AdSense Ads WordPress plugin through 2.8.18 allows unauthenticated attackers to inject arbitrary script through the 's' search parameter, which executes in a victim's browser if they are tricked into clicking a crafted link. Real-world exploitation is constrained by two gates: an administrator must have configured at least one block using the {title} or {short-title} placeholder with that block enabled on search pages (a documented but non-default setting), and a victim must interact with the malicious URL (CVSS UI:R). No public exploit code has been identified at time of analysis, and no EPSS score or CISA KEV entry was provided; the issue is fixed in version 2.8.19.
RemediationAI
Vendor-released patch: upgrade the Ad Inserter plugin to version 2.8.19 or later, which contains the escaping/sanitization fix; confirm the update via the WordPress admin Plugins page or WP-CLI (wp plugin update ad-inserter). If immediate upgrading is not possible, disable the block(s) that use the {title} or {short-title} placeholder on search pages, or restrict those blocks from running on search-result templates - the trade-off is that intended ad output on search pages will be suppressed. As a temporary compensating control, deploy a WAF rule that rejects or escapes requests whose 's' parameter contains HTML/script metacharacters, but note this can break legitimate search queries and should be treated as a stopgap only. Because exploitation requires a victim to click a crafted search URL (UI:R), awareness and link-filtering measures help but do not replace patching. Reference the Wordfence advisory and the Trac 2.8.19 changeset for exact code changes.
Affected VersionsENISA
Affected Packages
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
The flaw is a reflected XSS (CWE-79) in the WordPress plugin 'Ad Inserter - Ad Manager & AdSense Ads' (CPE cpe:2.3:a:spacetime:ad_inserter_-_ad_manager_&_adsense_ads), tracked as CVE-2026-89427 with assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N. WordPress passes search input via the 's' query parameter; when the plugin renders a block that uses the {title} or {short-title} placeholder on search-result pages, that user-supplied string is placed into the page without sufficient sanitization and output escaping, allowing script injection into the HTML response. Referenced source lines in ad-inserter.php (12903, 13012, 13081 at tag 2.8.18) point to the placeholder-handling and search-page rendering paths where the missing escaping occurs. The scope-change (S:C) reflects that the injected script runs in the origin of the affected WordPress site, not merely within a third-party ad frame.
Know when Wordpress Plugin 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
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Reflected XSS: network, low complexity, unauthenticated attacker, but requires victim click (UI:R); payload crosses into victim's browser context (S:C) with limited C/I impact and no availability effect.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Ad Inserter - Ad Manager & AdSense Ads plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via 's' Search Parameter in all versions up to, and including, 2.8.18 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. Exploitation requires that a site administrator has configured at least one Ad Inserter block using the {title} or {short-title} placeholder with that block enabled for search pages, which is a standard, documented plugin feature.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
EUVD-2026-90572
GHSA-cjx2-r3r5-6cq4
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB