Skip to main content

Advanced Ads EUVDEUVD-2026-91340

| CVE-2026-94180 MEDIUM
Authorization Bypass Through User-Controlled Key (CWE-639)
2026-10-02 Patchstack GHSA-j899-v3p9-97f4
4.3
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

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

  1. Access
    Authenticate as low-privileged WordPress user
  2. Delivery
    Identify user-controlled key parameter
  3. Exploit
    Substitute another object's identifier
  4. Execution
    Bypass authorization check (CWE-639)
  5. Impact
    Retrieve embedded sensitive data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
Exploitation Conditions

Exploitation requires an authenticated WordPress account on a site running the Advanced Ads plugin version 2.0.26 or earlier (PR:L indicates at least low-privilege credentials are needed - not anonymous). The attacker must manipulate a user-controlled key/identifier parameter that the plugin fails to authorize against the requesting user. Limiting factors: valid (even low-tier) authentication is mandatory, impact is confined to disclosure of embedded sensitive data (C:L, no integrity or availability impact), and exploitation is bounded to whatever sensitive fields the vulnerable object reference exposes. No special non-default configuration is indicated by the description.

Impact

This is a moderate-severity (CVSS 4.3) authorization bypass in the Advanced Ads WordPress plugin. The provided CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) indicates network-reachable, low-complexity exploitation requiring low-level authentication (PR:L), with only limited confidentiality impact and no integrity or availability impact - consistent with an IDOR-style (CWE-639) read of embedded sensitive data rather than full compromise. No EPSS score, KEV listing, or POC reference was provided in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The limited confidentiality-only impact plus the authentication requirement means this is a real but low-priority issue for most defenders: it warrants patching in the normal maintenance cycle rather than emergency response. No conflicting signals are present, but note that KEV/EPSS/POC data were entirely absent from the input and should be checked independently before final prioritization.

Exploit ScenarioDerived

A low-privileged authenticated user (e.g., a subscriber or contributor account on a WordPress site running Advanced Ads ≤2.0.26) manipulates a user-controlled identifier in a plugin request to reference objects they do not own. Because the plugin fails to verify ownership/authorization for the supplied key (CWE-639), the attacker retrieves embedded sensitive data belonging to other users or ad configurations. No public proof-of-concept was referenced in the provided data.

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

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

Alert me

AnalysisAIv1 – Oct 02, 2026

Embedded sensitive data exposure in the Monetizemore Advanced Ads WordPress plugin (versions through 2.0.26) allows an authenticated low-privilege user to retrieve sensitive data embedded in plugin-controlled objects by manipulating a user-controlled key or identifier. The flaw is a CWE-639 authorization bypass (IDOR-style) rated CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N), meaning exploitation is network-reachable but requires at least low-tier authenticated credentials and yields confidentiality-only impact. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis; the issue was reported through the Patchstack vulnerability disclosure program.

RemediationAI

No vendor-released patch was identified in the provided intelligence at time of analysis; the advisory enumerates 2.0.26 as the latest affected release, so site operators should watch the vendor and the Patchstack entry (https://patchstack.com/database/wordpress/plugin/advanced-ads/vulnerability/wordpress-advanced-ads-plugin-2-0-26-sensitive-data-exposure-vulnerability?_s_id=cve) for a fixed version and apply it immediately when published, verifying the installed version afterward. Until then, apply compensating controls: audit and reduce the number of low-privilege accounts (subscribers, contributors, authors) that could reach the vulnerable handler, since exploitation requires valid authentication (PR:L) - the trade-off is that tighter role hygiene can disrupt legitimate editorial workflows. If Advanced Ads is not actively used, deactivate and remove it, which eliminates exposure entirely at the cost of losing its ad-management features; if it is required, consider restricting access to WordPress admin/AJAX endpoints by IP or placing the site behind a WAF rule that blocks enumeration-style requests to the plugin's object-lookup endpoints. Because the impact is read-only disclosure (C:L, no I or A impact), the data exposed should also be treated as potentially compromised and rotated if it includes credentials or other secrets. Administrators should additionally enable logging on plugin endpoints to detect identifier-enumeration patterns while awaiting a vendor fix.

Affected VersionsENISA

Advanced Ads n/a ≤2.0.26

Affected Packages

euvd advanced_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

The root cause is CWE-639, Authorization Bypass Through User-Controlled Key, a classic insecure direct object reference (IDOR) pattern. In Advanced Ads, a WordPress advertising-management plugin identified by the CPE string cpe:2.3:a:monetizemore:advanced_ads, the plugin accepts a client-supplied key or identifier when looking up an object (for example an ad, placement, or configuration record) and fails to verify that the requesting user is authorized to access that specific object before returning its contents. Because the check is missing rather than merely weak, an attacker who is already logged in at a low privilege level (PR:L in the assessed vector) can enumerate or guess identifiers to read data belonging to other users or to the site itself. WordPress plugin data flows through AJAX and REST-style endpoints guarded by capability checks and nonces; when a handler performs only a presence/format validation on the key instead of an ownership or capability check, any authenticated account that can reach the endpoint can trigger disclosure. The impact is scoped to confidentiality (C:L) with no integrity or availability effect, and the data exposed is limited to whatever sensitive fields the vulnerable object reference returns - there is no indication of privilege escalation, code execution, or modification of stored content.

Know when Advanced Ads 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 (Patchstack) PRIMARY 4.3 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
vuln.today AI 4.3 MEDIUM

Network-reachable IDOR requiring low-privilege authentication (PR:L) with no user interaction; only limited sensitive-data disclosure, so C:L and I/A:N.

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

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

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

DescriptionCVE.org

Authorization Bypass Through User-Controlled Key vulnerability in Monetizemore Advanced Ads allows Retrieve Embedded Sensitive Data.

This issue affects Advanced Ads: from n/a through 2.0.26.

Threat Intelligence Overview

EPSS Score
0.3%
Top 81% exploitable
Prevalence
Medium
common WordPress ad-management plugin, but not universal across sites
Data Quality
4 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.3%
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
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

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

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

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

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