CVE-2024-52488

Multiple Themes - Authenticated (Subscriber+) Arbitrary Plugin Activation and Deactivation

2024-11-20 00:00
Kévin Mosbahi (Mika)

Strategic Overview

Status
Unpatched
Affected Theme
Grip
Affected Version
<= 1.0.9
CVSS
8.8High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-52488
View all Grip vulnerabilities

At a glance

CVE-2024-52488 is a high-severity Missing Authorization vulnerability in the Grip WordPress theme, affecting versions <= 1.0.9. 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. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed November 2024, reported by Kévin Mosbahi (Mika).

Vulnerability Overview

Several themes are vulnerable to unauthorized access to functionality in various versions. This makes it possible for authenticated attackers, with Subscriber-level access and above, to activate or deactivate arbitrary plugins, which may make arbitrary code execution possible.

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

Reaching this weakness in Grip <= 1.0.9 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. No fixed build of this theme is recorded for Grip yet, so installs running <= 1.0.9 stay exposed until the vendor ships one.

Remediation

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

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. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Login Security
  • Alerts

External References

Related records

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