Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-1399: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in miles99 WP Google Ad Manager Plugin

0
Medium
VulnerabilityCVE-2026-1399cvecve-2026-1399cwe-79
Published: Wed Jan 28 2026 (01/28/2026, 11:23:42 UTC)
Source: CVE Database V5
Vendor/Project: miles99
Product: WP Google Ad Manager Plugin

Description

The WP Google Ad Manager Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 1.1.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/26/2026, 19:09:17 UTC

Technical Analysis

CVE-2026-1399 is a stored cross-site scripting (XSS) vulnerability classified under CWE-79, found in the WP Google Ad Manager Plugin developed by miles99 for WordPress. The vulnerability exists due to improper input sanitization and insufficient output escaping in the plugin's administrative settings interface. This flaw allows an authenticated attacker with administrator-level permissions or higher to inject arbitrary JavaScript code into pages managed by the plugin. The malicious scripts are stored persistently and execute whenever a user accesses the affected page, potentially compromising user sessions or enabling unauthorized actions. The vulnerability specifically affects multi-site WordPress installations or those where the unfiltered_html capability is disabled, limiting the scope of impact. The CVSS 3.1 base score is 4.4, indicating medium severity, with the vector reflecting network attack vector, high attack complexity, required privileges at the administrator level, no user interaction, and a scope change. Although no known exploits are currently reported in the wild, the vulnerability poses a risk to sites using this plugin in the specified configurations. The lack of patch links suggests that a fix may not yet be publicly available, emphasizing the need for cautious administrative controls and monitoring.

Potential Impact

The primary impact of this vulnerability is the potential for stored cross-site scripting attacks, which can lead to unauthorized script execution within the context of affected WordPress sites. This can compromise the confidentiality and integrity of administrative sessions, potentially allowing attackers to hijack sessions, deface websites, or perform unauthorized actions with administrator privileges. Since the vulnerability requires administrator-level access to exploit, the risk is somewhat mitigated by the need for high privileges; however, insider threats or compromised administrator accounts could leverage this flaw. The vulnerability does not affect availability directly but can degrade trust and operational integrity of affected sites. Multi-site WordPress installations and those with unfiltered_html disabled are at particular risk, which may include large organizations or managed hosting providers. The absence of known exploits reduces immediate risk but does not eliminate the potential for future attacks once exploit code becomes available.

Mitigation Recommendations

To mitigate CVE-2026-1399, organizations should first verify if they are running the WP Google Ad Manager Plugin on multi-site WordPress installations or with unfiltered_html disabled. Since no official patches are currently linked, administrators should restrict plugin access strictly to trusted users and review administrator accounts for compromise. Implementing strict input validation and output escaping in custom plugin code or applying temporary filters to sanitize admin inputs can reduce risk. Monitoring administrative activity logs for unusual changes in plugin settings is recommended. Consider disabling or removing the plugin if it is not essential. Additionally, maintaining up-to-date backups and preparing for rapid patch deployment once an official fix is released will help minimize impact. Employing web application firewalls (WAFs) with rules to detect and block XSS payloads targeting the plugin's admin pages can provide an additional layer of defense.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2026-01-23T21:34:55.715Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6979f49e4623b1157cb3655c

Added to database: 1/28/2026, 11:35:58 AM

Last enriched: 2/26/2026, 7:09:17 PM

Last updated: 3/24/2026, 10:27:19 AM

Views: 58

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses