CVE-2026-116404

The Redux Framework plugin for WordPress is vulnerable to authorization bypass in versions up to and including 4.5.15 due to improper verification of user authorization. An authenticated attacker with subscriber-level access or higher can view the entire Redux options payload, including plaintext password values, API keys, license keys, and SMTP credentials, exposed in the inline JavaScript block on the profile page. The Users extension is loaded automatically for every Redux instance, so any site running Redux Framework is affected.

The Redux Framework plugin for WordPress (all versions up to and including 4.5.11) is vulnerable to privilege escalation. This is due to the plugin saving arbitrary meta keys under a registered option name without sufficient capability checks or key allowlist restrictions, allowing authenticated attackers with Subscriber-level access and above to set an arbitrary role (e.g., Administrator) during a profile update if a plugin or theme using this framework has added at least one user profile field leveraging Redux_Users::set_profile/set_section/set_field.

The Redux Framework plugin for WordPress is vulnerable to Stored Cross-Site Scripting via User Meta Merge via 'user-mediaurl' Media Field in all versions up to, and including, 4.5.14 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is exploitable by Subscriber-level users who can store a payload in user meta fields such as the biography, session_tokens (via a crafted User-Agent at login), or persisted_preferences (via the REST API), which are then promoted to the site-wide redux_demo option when a media URL repair is triggered on the demo panel.

The Redux Framework plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the spinner field in versions up to and including 4.5.13 due to insufficient input sanitization and output escaping. In the user_meta_save() function scalar values bypass the sanitization logic that only processes arrays, allowing the spinner field value to be stored in user meta without proper sanitization. Later, this value is rendered in an unquoted HTML attribute without escaping, enabling authenticated attackers with subscriber-level access and above to inject arbitrary web scripts.

The Redux Framework plugin for WordPress in versions up to and including 4.5.13 is vulnerable to Stored Cross-Site Scripting via the Media field filter values due to insufficient input sanitization of nested array values in the user_meta_save() function and unsafe output of filter CSS values in the render() function without proper escaping. Authenticated attackers with subscriber-level access and above can inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

The Redux Framework plugin for WordPress in versions up to and including 4.5.13.1 is vulnerable to stored cross-site scripting via the Slider field in User Profile settings. This is due to insufficient input sanitization in the user_meta_save() function and improper output escaping in the Redux_Slider::render() method. An authenticated attacker with Subscriber-level access or above can inject arbitrary scripts into their profile that execute when an Administrator views the attacker's profile page.

The Redux Framework WordPress plugin before version 4.5.13 does not restrict which user meta keys can be written when saving custom profile fields. This allows users with at least the Subscriber role to escalate their privileges to Administrator by submitting a crafted value while updating their own profile, on sites where the Redux Framework WordPress plugin before 4.5.13's user-profile (Users extension) feature is enabled.

The Redux Framework plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'data' parameter in all versions up to and including 4.5.8 due to insufficient input sanitization and output escaping. This allows authenticated attackers with Contributor-level access and above to inject arbitrary web scripts that execute when a user accesses an injected page.