Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain subscriber-level account
-
ExploitSend request to unprotected plugin action
-
ExecutionBypass missing capability check
-
ImpactRead or modify privileged data
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 the attacker to hold a Subscriber-level (low-privilege authenticated) account on a WordPress site running Wordable version 8.2.10 or earlier; the plugin fails to enforce authorization (capability) checks on one or more actions, so an authenticated low-privilege user can reach functionality intended for higher roles. The primary limiting factor is the authentication requirement (PR:L): the attacker must already have, or be able to register, an account - so the practical risk is far higher on sites that allow open user self-registration than on sites that restrict account creation. No special non-default plugin configuration is indicated by the available data; user interaction is not required (UI:N). |
| Impact | This is a genuine priority-tier vulnerability but with an important access caveat. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N) describes a network-reachable, low-complexity flaw requiring only low privileges (PR:L) - consistent with the description's 'Subscriber' qualifier, meaning the attacker must hold at least a subscriber-level WordPress account. Impact is high to confidentiality and integrity (C:H/I:H) with no availability impact (A:N), yielding a base score of 8.1. Signal cross-reference is limited: no EPSS probability, no CISA KEV listing, and no public POC were provided, so there is no evidence of active or imminent widespread exploitation despite the high base score. The risk is therefore real but contingent - on sites that permit open user registration (a common WordPress default for many deployments), a subscriber account is trivial to obtain, which materially lowers the practical bar implied by PR:L; on sites that disable self-registration, exploitation requires an attacker to first acquire a low-privilege account, making this closer to an insider or post-compromise escalation issue. No conflicting signals were found, but the exploitation-likelihood picture is incomplete due to missing EPSS/KEV/POC data. |
| Exploit ScenarioDerived | An attacker registers or obtains a low-privilege subscriber account on a WordPress site running Wordable 8.2.10 or earlier, then invokes plugin actions that lack proper authorization (capability) checks. Because the missing-authorization flaw (CWE-862) exposes functions meant for higher-privileged users, the subscriber can read or alter data they should not access, such as plugin configuration or content-export operations. No public exploit code was identified at the time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 10, 2026
Broken access control in the Wordable WordPress plugin (versions up to and including 8.2.10) lets any authenticated Subscriber-level account invoke functionality that should be reserved for higher-privileged roles, yielding high confidentiality and integrity impact (CVSS 8.1, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N). Reported by Patchstack and rooted in a missing-authorization condition (CWE-862), the issue requires the attacker to already hold or be able to register a low-privilege account, so real-world risk is much greater on sites permitting open user self-registration than on sites where account creation is locked down. No public exploit code was identified at the time of analysis, the CVE is not listed in CISA KEV, and no EPSS data was supplied; treated as a genuine priority-tier vulnerability with a meaningful authentication caveat, it warrants prompt review of plugin exposure and user-registration settings.
RemediationAI
The provided data does not identify a fixed Wordable release, so the first step is to check the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/wordable/vulnerability/wordpress-wordable-plugin-8-2-10-broken-access-control-vulnerability?_s_id=cve) and the plugin's own changelog for a version newer than 8.2.10 and upgrade as soon as one is published - no vendor-released patch is identified at the time of analysis, so do not assume 8.2.10 is the last affected build without confirming with the vendor. If no patched build exists and the plugin's functionality is not business-critical, deactivate and remove it; the trade-off is loss of the Wordable content-publishing integration, but it eliminates the exposed attack surface entirely. Where the plugin must remain, two controls materially reduce exposure: disable open self-registration in WordPress (Settings → General, uncheck 'Anyone can register') so an attacker cannot self-provision the Subscriber account the exploit requires - the trade-off is that legitimate self-service signups must be handled manually - and audit existing accounts, removing or downgrading unused Subscriber users so the pool of potentially malicious low-privilege accounts is minimized. Deploying a virtual patch or WAF rule that blocks unauthenticated or Subscriber-level requests to the plugin's AJAX/REST endpoints adds a compensating layer, with the caveat that aggressive blocking can break legitimate plugin workflows and generate false positives. Finally, enable and review audit logging for privileged plugin actions so any abuse from a Subscriber-level account is detected quickly, and re-check the advisory periodically in case an official patched version is released.
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
Wordable is a WordPress plugin, and the affected component is best described by the CPE cpe:2.3:a:wordable:wordable:*:*:*:*:*:*:*:* (Wildcard versioning, indicating the advisory covers the entire plugin line up to the stated 8.2.10 ceiling). The root cause class is CWE-862, Missing Authorization: one or more plugin actions - typically AJAX handlers, REST API routes, or admin-post endpoints - perform privileged operations without verifying that the calling user holds the required WordPress capability. WordPress ships a role/capability model in which a Subscriber has essentially only the 'read' capability, so a correct implementation would call current_user_can() with an appropriate capability (and usually validate a nonce) before executing sensitive logic; without that check, the plugin trusts the request path rather than the caller's identity. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N confirms the attack is network-reachable over standard HTTP(S), needs no special conditions or user interaction, and is confined to the plugin's own security scope while still allowing high-impact reads and writes. The reported vector and the independent assessment agree exactly, and no non-default configuration prerequisite is indicated in the available data.
Know when Wordable 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:H/I:H/A:N
Network-reachable missing-authorization flaw exploitable by any authenticated Subscriber (PR:L), low complexity, no UI; high confidentiality/integrity impact but no availability effect.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Subscriber Broken Access Control in Wordable <= 8.2.10 versions.
Executive ViewAI
The Wordable WordPress plugin (versions up to and including 8.2.10) contains a broken access control flaw that allows any authenticated Subscriber-level user to perform actions reserved for higher-privileged roles, potentially exposing sensitive data and allowing unauthorized modifications. Organizations running affected versions on sites with open user registration face the greatest risk, as attackers can self-register and exploit the flaw without needing existing credentials. Leadership should prioritize reviewing plugin necessity and user-registration settings to mitigate potential data integrity and confidentiality breaches.
No vendor-released patch identified at time of analysis. Interim mitigations: disable the Wordable plugin if not essential; restrict or disable open user registration; audit and remove unnecessary Subscriber-level accounts; deploy WAF rules to block unauthorized requests to vulnerable endpoints; monitor logs for privilege escalation; enforce least privilege for all WordPress roles.
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-96538
GHSA-9q6p-p247-9mrr
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB