CVE-2024-11816

The Ultimate WordPress Toolkit – WP Extended <= 3.0.11 - Missing Authorization to Authenticated (Subscriber+) Remote Code Execution

2025-01-07 00:00
stealthcopter

Strategic Overview

Status
Patched in 3.0.12
Affected Plugin
WP Extended – The Ultimate WordPress Toolkit
Affected Version
<= 3.0.11
CVSS
8.8High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-11816
View all WP Extended – The Ultimate WordPress Toolkit vulnerabilities

At a glance

CVE-2024-11816 is a high-severity Missing Authorization vulnerability in the WP Extended WordPress plugin, affecting versions <= 3.0.11. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.0.12; sites on affected versions should update now. Disclosed January 2025, reported by stealthcopter.

Vulnerability Overview

The Ultimate WordPress Toolkit – WP Extended plugin for WordPress is vulnerable to Remote Code Execution in version 3.0.11. This is due to a missing capability check on the 'wpext_handle_snippet_update' function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to execute code on the server providing an admin has created at least one code snippet.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-862: Missing Authorization

WP Extended <= 3.0.11 carries this weakness at wpext_handle_snippet_update, and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WP Extended the fix is 3.0.12: builds <= 3.0.11 are affected, anything from 3.0.12 onward is not.

Remediation

Update to version 3.0.12, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WP Extended 3.0.12 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-11816https://www.wordfence.com/threat-intel/vulnerabilities/id/b3ce53e5-8666-4227-83d3-58f35db0ce68https://nvd.nist.gov/vuln/detail/CVE-2024-11816

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C