CVE-2026-39533
Description
Unauthenticated broken access control in AWP Classifieds ≤4.4.4 allows unprivileged users to perform higher privileged actions; update to 4.4.5.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Unauthenticated broken access control in AWP Classifieds ≤4.4.4 allows unprivileged users to perform higher privileged actions; update to 4.4.5.
Vulnerability
AWP Classifieds plugin for WordPress versions up to 4.4.4 contains a broken access control vulnerability due to missing authorization or authentication checks in a function, allowing unauthenticated users to execute actions reserved for higher privileged roles [1]. The specific function lacks nonce token or capability checks, making the code path reachable without any prior authentication.
Exploitation
An attacker with no authentication or any special network position can send crafted HTTP requests to the vulnerable endpoint. No user interaction or race window is required. The attacker simply needs to access the exposed function that should be protected by authorization; the missing check allows the request to succeed [1].
Impact
Successful exploitation leads to unauthorized execution of privileged actions, which can result in information disclosure, modification of data, or further compromise of the WordPress installation. The CVSS score of 7.5 indicates high severity, and the vulnerability is expected to be used in mass exploitation campaigns [1].
Mitigation
Update to version 4.4.5 or later, released to resolve the vulnerability [1]. If unable to update immediately, apply a mitigation rule from Patchstack to block attacks until the update is deployed. Consider enabling auto-updates for vulnerable plugins if using Patchstack [1].
AI Insight generated on Jun 15, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1- Range: <=4.4.4
Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
1News mentions
0No linked articles in our index yet.