CVE-2025-54049

Custom API for WP <= 4.2.2 - Authenticated (Subscriber+) Privilege Escalation

2025-07-28 00:00
Hiro

Strategic Overview

Status
Patched in 4.2.3
Affected Plugin
Custom API for WP
Affected Version
<= 4.2.2
CVSS
8.8High
Weakness type
CWE-266 · Incorrect Privilege Assignment
CVE
CVE-2025-54049
View all Custom API for WP vulnerabilities

At a glance

CVE-2025-54049 is a high-severity Incorrect Privilege Assignment vulnerability in the Custom API for WP WordPress plugin, affecting versions <= 4.2.2. 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 4.2.3; sites on affected versions should update now. Disclosed July 2025, reported by Hiro.

Vulnerability Overview

The Custom API for WP plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 4.2.2. This is due to the plugin not properly restricting a users ability to set roles. This makes it possible for authenticated attackers, with Subscriber-level access and above, to elevate their privileges.

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-266: Incorrect Privilege Assignment

A product incorrectly assigns a privilege to a particular actor, creating an unintended sphere of control for that actor.

Remediation

Update to version 4.2.3, 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: Custom API for WP 4.2.3 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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