CVE-2026-110705: missing authz exposes admin

CISO Take

The Redux Framework plugin for WordPress (up to 4.5.16) fails to check authorization on its import/export extension, so any logged-in subscriber can download the full options panel configuration, which may include API keys, SMTP credentials, licence keys and third-party tokens. The risk is moderate (CVSS 5.3, high attack complexity) because the site must register a Redux import_export field on user profiles via Redux_Users::set_profile(), which is what leaks the nonce into the subscriber's profile page. There is no CISA KEV listing, no public exploit and no Nuclei template, and EPSS data is not yet available, so there is no evidence of active exploitation. The AI relevance is indirect: it matters only where WordPress sites hosting AI chatbots, ML dashboards or LLM-powered plugins keep provider API keys in Redux options. Upgrade to 4.5.17 or later, and rotate any secrets stored in Redux options on sites that allow open registration and use the profile-based import/export field.

Sources:NVDATLASwordfence.complugins.trac.wordpress.org

What is the risk?

Medium. Exploitation needs a low-privilege authenticated account (often self-registered) and a non-default configuration that exposes the nonce on the profile page. Impact is confined to confidentiality (C:H) with no integrity or availability effect. Exposure rises sharply on sites with open subscriber registration. Stolen LLM provider keys could lead to cost abuse or data access. EPSS is unavailable and there is no public exploit or known exploitation.

How does the attack unfold?

Initial Access

Attacker registers or uses an existing subscriber-level account on the WordPress site.

AML.T0012

Nonce Discovery

Attacker reads the import/export nonce printed in the profile.php page source.

Exploitation

Attacker calls the Redux export action, which lacks an authorization check, to download the full options configuration.

AML.T0049

Impact

Exposed API keys, SMTP credentials and tokens are used for AI service abuse and lateral access.

AML.T0055

Initial Access

Attacker registers or uses an existing subscriber-level account on the WordPress site.

AML.T0012

Nonce Discovery

Attacker reads the import/export nonce printed in the profile.php page source.

Exploitation

Attacker calls the Redux export action, which lacks an authorization check, to download the full options configuration.

AML.T0049

Impact

Exposed API keys, SMTP credentials and tokens are used for AI service abuse and lateral access.

AML.T0055

How severe is it?

CVSS 3.1

5.3 / 10

EPSS

N/A

Exploitation Status

No known exploitation

Sophistication

Moderate

What is the attack surface?

AVNetwork

ACHigh

PRLow

UINone

SUnchanged

CHigh

INone

ANone

What should I do?

5 steps

Update Redux Framework to 4.5.17 or later.
If patching is delayed, remove the import_export field from user profile registration (Redux_Users::set_profile()) and restrict open user registration or the default subscriber role.
Rotate all API keys, SMTP credentials, licence keys and tokens stored in Redux options, especially LLM provider keys, and review provider usage logs for anomalies.
Audit subscriber-level accounts for suspicious ones.
Monitor web logs for requests from low-privilege users to Redux import/export actions and profile.php nonce use.

How is it classified?

Auth BypassData LeakagePluginAPIAML.T0012- Valid Accounts AML.T0049- Exploit Public-Facing Application AML.T0055- Unsecured Credentials

Which compliance frameworks are affected?

This CVE is relevant to:

ISO 42001

A.10.3-Suppliers

NIST AI RMF

MANAGE 2.3-Risk treatment and response to unknown risks

OWASP LLM Top 10

LLM03-Supply Chain

Frequently Asked Questions

What is CVE-2026-110705?

The Redux Framework plugin for WordPress (up to 4.5.16) fails to check authorization on its import/export extension, so any logged-in subscriber can download the full options panel configuration, which may include API keys, SMTP credentials, licence keys and third-party tokens. The risk is moderate (CVSS 5.3, high attack complexity) because the site must register a Redux import_export field on user profiles via Redux_Users::set_profile(), which is what leaks the nonce into the subscriber's profile page. There is no CISA KEV listing, no public exploit and no Nuclei template, and EPSS data is not yet available, so there is no evidence of active exploitation. The AI relevance is indirect: it matters only where WordPress sites hosting AI chatbots, ML dashboards or LLM-powered plugins keep provider API keys in Redux options. Upgrade to 4.5.17 or later, and rotate any secrets stored in Redux options on sites that allow open registration and use the profile-based import/export field.

Is CVE-2026-110705 actively exploited?

No confirmed active exploitation of CVE-2026-110705 has been reported, but organizations should still patch proactively.

How to fix CVE-2026-110705?

1. Update Redux Framework to 4.5.17 or later. 2. If patching is delayed, remove the import_export field from user profile registration (Redux_Users::set_profile()) and restrict open user registration or the default subscriber role. 3. Rotate all API keys, SMTP credentials, licence keys and tokens stored in Redux options, especially LLM provider keys, and review provider usage logs for anomalies. 4. Audit subscriber-level accounts for suspicious ones. 5. Monitor web logs for requests from low-privilege users to Redux import/export actions and profile.php nonce use.

What systems are affected by CVE-2026-110705?

This vulnerability affects the following AI/ML architecture patterns: WordPress-hosted AI chatbot plugins, LLM API integrations, ML web dashboards.

What is the CVSS score for CVE-2026-110705?

CVE-2026-110705 has a CVSS v3.1 base score of 5.3 (MEDIUM).

What is the AI security impact?

Affected AI Architectures

WordPress-hosted AI chatbot pluginsLLM API integrationsML web dashboards

MITRE ATLAS Techniques

AML.T0012Valid Accounts

AML.T0049Exploit Public-Facing Application

AML.T0055Unsecured Credentials

Compliance Controls Affected

ISO 42001: A.10.3

NIST AI RMF: MANAGE 2.3

OWASP LLM Top 10: LLM03

What are the technical details?

Original Advisory

The Redux Framework plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 4.5.16. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to export the entire Redux options panel configuration — including API keys, SMTP credentials, licence keys, and third-party tokens — that is otherwise restricted to administrators. Exploitation requires that a theme or plugin registers a Redux import_export field on a user profile via Redux_Users::set_profile(), which causes the nonce to be printed into the subscriber's own /wp-admin/profile.php page source, making it directly readable without any additional privileges.

Exploitation Scenario

An attacker registers a subscriber account on a WordPress site whose AI chatbot theme exposes a Redux import_export field on user profiles. They open /wp-admin/profile.php, read the export nonce from the page source, and call the import/export action to download the full options configuration. The export contains an LLM provider API key and SMTP credentials. The attacker then uses the key to run inference at the site owner's expense or to reach linked services, and uses the SMTP credentials to send phishing email.

Weaknesses (CWE)

CWE-862Missing AuthorizationPrimary CWE-862Missing Authorization

CWE-862 — Missing Authorization: The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

[Architecture and Design] Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
[Architecture and Design] Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor [REF-7].

Source: MITRE CWE corpus.