Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privileged account on target WordPress site
-
DeliverySend request to under-protected plugin endpoint
-
ExploitMissing authorization check bypassed
-
ExecutionPerform restricted action without capability
-
ImpactModify data or disrupt availability
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated account on the target WordPress site (CVSS PR:L), so the realistic prerequisite is either open user registration or an attacker-controlled low-privileged account; the affected version range is Advanced Post Manager from n/a through 4.5.6. The limiting factor is that fully unauthenticated attackers cannot exploit this directly - some valid session is needed - which narrows exposure on sites that disable public registration and restrict account provisioning. The input description does not name the specific vulnerable endpoint, feature, or configuration setting, so the exact triggering action could not be extracted and should be read from the Patchstack advisory. |
| Impact | This is a moderate-priority issue rather than a top-tier emergency. The provided CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H, base 7.1) indicates a network-reachable, low-complexity flaw requiring low-privilege authentication (PR:L) and no user interaction, which for a WordPress plugin typically means any authenticated account (e.g., subscriber/contributor) can trigger it. The CWE-862 Missing Authorization root cause is consistent with a broken-access-control weakness reported by Patchstack. No EPSS score, CISA KEV listing, SSVC decision data, or POC was supplied, so exploitation status is 'no public exploit identified at time of analysis' and there is no evidence of active exploitation. Note a conflict worth verifying: the input vector asserts A:H (high availability impact) with C:N/I:L, which is unusual for a generic missing-authorization flaw in a content-management plugin - a broken-access-control issue more commonly yields unauthorized data modification (integrity) than full availability loss, so the A:H rating should be verified against the Patchstack advisory. Because exploitation requires an authenticated (if low-privileged) account, real-world risk is meaningfully lower than an unauthenticated RCE despite the 7.1 score. |
| Exploit ScenarioDerived | An attacker who holds a low-privileged authenticated account on a WordPress site running Advanced Post Manager ≤4.5.6 (for example a self-registered subscriber on a site with open registration) sends a request to a plugin endpoint that fails to verify the caller's authorization. Lacking the proper capability check, the plugin performs a restricted action on the attacker's behalf. No public exploit code was identified at time of analysis, and no user interaction is required. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 16, 2026
Missing authorization checks in the Advanced Post Manager WordPress plugin through version 4.5.6 let an authenticated user invoke functionality that should be reserved for higher-privileged roles, weakening the site's access-control boundary. Exploitation requires a valid low-privileged session (CVSS PR:L), so realistic exposure exists mainly on sites with open registration or attacker-controlled accounts, and no public exploit code has been identified at time of analysis. The demonstrated impact is limited to integrity and availability (C:N/I:L/A:L per our assessment), which is why this reads as a moderate-priority issue rather than a top-tier emergency.
RemediationAI
No vendor-released patch was identified at time of analysis, so the primary action is to confirm the current version against the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/advanced-post-manager/vulnerability/wordpress-advanced-post-manager-plugin-4-5-6-broken-access-control-vulnerability?_s_id=cve) and upgrade as soon as a fixed release is published; if the plugin is not essential, deactivating and removing it eliminates the exposure entirely, at the cost of losing its post-management features. Where the plugin must stay, apply compensating controls: turn off public registration and close self-service account creation (Settings > General, uncheck 'Anyone can register') and treat this as a real prerequisite, since without a low-privileged account the flaw is not reachable - the trade-off is loss of open sign-ups; audit existing users and remove unused subscriber/contributor accounts to shrink the pool of usable sessions; and add a WAF or gateway rule that blocks low-privileged requests to the plugin's admin-ajax/REST/admin-post handlers until a patch lands, accepting the risk of false positives against legitimate editorial workflows. Also monitor logs for unexpected post, taxonomy, or option changes made by low-privilege accounts, as these are the observable signs of successful exploitation.
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 affected component is the Advanced Post Manager plugin (WordPress slug advanced-post-manager), maintained under the Liquid Web / StellarWP umbrella and tracked by CPE cpe:2.3:a:liquid_web_/_stellarwp:advanced_post_manager. The root cause is CWE-862 (Missing Authorization): one or more plugin operations rely on incorrectly configured or absent access-control checks, so a request from a low-privileged user is processed with the privileges of the underlying functionality rather than being rejected. In WordPress terms this typically means a missing current_user_can() capability check or an improper nonce/capability combination on an AJAX, REST, or admin-post handler. Our assessed vector, CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L, indicates the flaw is reachable over the network without user interaction, but only after authentication, and that successful abuse alters data or reduces availability rather than exposing secrets; note this diverges from the vendor-reported 7.1 (A:H), and the lower availability weighting should guide triage. The advisory does not disclose the specific endpoint or setting that is misconfigured, so the exact triggering action must be read from the Patchstack entry.
Know when Advanced Post Manager 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:L/UI:N/S:U/C:N/I:L/A:H
Network-reachable missing-authorization flaw needing a low-privileged account (PR:L); impact assessed as integrity/availability low since generic broken access control rarely causes full availability loss, downgrading the input's A:H.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Missing Authorization vulnerability in Liquid Web / StellarWP Advanced Post Manager advanced-post-manager allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Advanced Post Manager: from n/a through 4.5.6.
Executive ViewAI
The Advanced Post Manager WordPress plugin through version 4.5.6 contains a missing authorization flaw that allows an authenticated low-privileged user to perform actions intended for higher-privileged roles, potentially enabling unauthorized content or configuration changes on affected sites. This primarily affects WordPress sites using the plugin, especially those with open registration or attacker-controlled accounts. With no vendor-released patch identified at time of analysis and no public exploit identified at time of analysis, leadership should treat this as a moderate-priority access-control risk requiring immediate exposure reduction and monitoring rather than emergency incident response.
No vendor-released patch identified at time of analysis; interim mitigations include deactivating or removing the Advanced Post Manager plugin, restricting or disabling open registration, enforcing least privilege, auditing low-privileged accounts, monitoring for unauthorized changes, and applying WAF or virtual patching rules where available.
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
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-102866
GHSA-ghh3-46wv-4fmv
NVD
CVE.org
Vulnrichment
Exploit-DB