Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as Subscriber-level user
-
ExploitSubmit crafted profile-update request
-
ExecutionWrite arbitrary role meta key via Redux_Users
-
ImpactGain Administrator privileges and site control
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Least privilege enforcement
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 three concrete conditions: (1) an authenticated account with at least Subscriber-level access; (2) an active plugin or theme that uses Redux Framework to register a user-profile field via Redux_Users::set_profile/set_section/set_field - this is a non-default integration requirement, not a core plugin feature, and is the primary limiting factor; and (3) a profile-update action through which arbitrary meta keys can be saved under the registered option name without capability checks or a key allowlist. The vulnerability is network-reachable and needs no user interaction from a victim, but the absence of the required profile-field integration makes a given site non-exploitable even with the plugin installed. |
| Impact | This is a credible but conditional privilege-escalation issue (CWE-269) rather than a drop-everything emergency. The input CVSS 3.1 vector (AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N, 6.8 Medium) is internally consistent with the description: AV:N reflects exploitation over an HTTP profile-update request, PR:L matches the stated Subscriber-level-and-above requirement, and AC:H reflects the key precondition that a plugin or theme built on Redux Framework must have registered at least one user-profile field via Redux_Users::set_profile/set_section/set_field. No EPSS score, KEV entry, or SSVC decision data was supplied, and no public exploit identified at time of analysis. Because Redux Framework is a developer library embedded in other themes/plugins rather than an end-user feature, actual exploitability depends on the downstream integration, so the real-world risk is narrower than the C:H/I:H impact alone suggests - but where the vulnerable profile-field pattern is present, a low-privileged user can escalate to Administrator, which is a full site-compromise outcome. Net: a genuine priority on sites that both run the plugin and expose a Redux-backed user-profile field, and a lower priority elsewhere. Note A:N in the supplied vector is arguably understated, since gaining the Administrator role yields full availability control as well. |
| Exploit ScenarioDerived | An attacker registers or already holds a Subscriber-level account on a WordPress site whose active theme or plugin uses Redux Framework to add a user-profile field. They submit a crafted profile-update request that writes an arbitrary meta key (such as the site's capabilities/role meta) under the plugin's registered option name, assigning themselves the Administrator role and taking over the site. No public exploit code was identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 09, 2026
Privilege escalation in the Redux Framework WordPress plugin through version 4.5.11 lets an authenticated attacker with only Subscriber-level access escalate to any role, including Administrator, by writing an arbitrary role value during a profile update. The flaw is conditionally exploitable: it only triggers on sites where an active plugin or theme has integrated Redux user-profile fields via Redux_Users::set_profile/set_section/set_field, which is a non-default integration requirement, so having the plugin installed alone is not sufficient. Wordfence rates this 6.8 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H), the attack requires no victim interaction and is network-reachable, and no public exploit code has been identified at time of analysis; the practical limiting factor is the required third-party profile-field integration.
RemediationAI
Upgrade the Redux Framework plugin to a release newer than 4.5.11 that incorporates the upstream changeset 3582185 (https://plugins.trac.wordpress.org/changeset/3582185/redux-framework); the changeset is the confirmed upstream fix, but the exact first patched tagged release version is not independently confirmed from the available data, so verify the installed version's changelog against that changeset before relying on it. If immediate upgrade is not possible, the most effective compensating control is to identify and temporarily disable any plugin or theme that registers Redux user-profile fields via Redux_Users::set_profile/set_section/set_field - this removes the exploitable path entirely because the vulnerability is unreachable without such an integration; the trade-off is loss of that custom profile functionality until patching. As a secondary control, audit and tighten site roles so untrusted users are not granted Subscriber-level accounts (and review any custom registration flows that auto-assign Subscriber), and monitor wp_usermeta/option writes for unexpected role or capability keys; both measures reduce exposure but do not fix the underlying missing capability check and key allowlist, so they should not be treated as a substitute for upgrading. Review the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/bbe52266-9ee1-47a8-a6df-7057b29e8098?source=cve for any updated fixed-version guidance.
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
Redux Framework is a widely bundled WordPress options/settings framework used by many themes and plugins; the affected component is its user-profile subsystem (Redux_Users), which exposes set_profile, set_section, and set_field helpers so integrators can attach custom profile fields to registered option names. The root cause maps to CWE-269 (Improper Privilege Management): when a profile update is processed, meta keys are persisted under the registered option name without a capability check against the field being written and without an allowlist restricting which keys may be set. Because the profile-update handler trusts caller-supplied key/value pairs, a low-privileged authenticated user can plant a role-bearing meta key (for example the WordPress capabilities/user-role key) and have it saved as if it were a legitimate registered field, resulting in a role change to Administrator. CPE data identifies the single affected package as cpe:2.3:a:davidanderson:redux_framework:*:*:*:*:*:*:*:* - the vendor namespace davidanderson is the Redux Framework publisher on WordPress.org. Exploitation is two-stage: the code weakness is present in the plugin, but the reachable attack path depends on a separate integrator having registered at least one profile field through Redux_Users, which is why the vendor rates attack complexity High.
Know when Redux Framework 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:H/PR:L/UI:N/S:U/C:H/I:H/A:N
AV:N via HTTP profile update, AC:H because a plugin/theme must register a Redux user-profile field, PR:L for Subscriber access; escalation to Administrator yields full C/I/A.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Redux Framework plugin for WordPress is vulnerable to privilege escalation in all versions up to, and including, 4.5.11. This is due to the plugin saving arbitrary meta keys under a registered option name without sufficient capability checks or key allowlist / restrictions. This makes it possible for authenticated attackers, with Subscriber-level access and above, to set an arbitrary role (e.g., Administrator) when performing a profile update if a plugin or theme using this framework has added at least one user profile field that leverages Redux_Users::set_profile/set_section/set_field.
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
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
More in Redux Framework
View allPrivilege escalation in the Redux Framework WordPress plugin before 4.5.13 allows authenticated Subscriber-level users t
Stored XSS in Redux Framework (WordPress plugin) through version 4.5.13.1 allows authenticated Subscriber-level users to
Stored cross-site scripting in the Redux Framework WordPress plugin affects versions up to and including 4.5.13, allowin
Stored cross-site scripting in the Redux Framework plugin for WordPress through version 4.5.13 lets an authenticated att
Stored cross-site scripting in the Redux Framework WordPress plugin affects all versions up to and including 4.5.14, let
An authorization bypass in the Redux Framework WordPress plugin, affecting all versions up to and including 4.5.14, lets
EUVD-2025-211057
GHSA-m6ch-xqmp-f54q
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB