CVE-2026-118187

PublishPress Revisions <= 4.3.0 - Authenticated (Contributor+) Insecure Direct Object Reference

2026-11-04 00:00
trangdld

Strategic Overview

Status
Patched in 4.3.1
Affected Plugin
PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes
Affected Version
<= 4.3.0
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-118187
View all PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes vulnerabilities

At a glance

CVE-2026-118187 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the PublishPress Revisions WordPress plugin, affecting versions <= 4.3.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 4.3.1; sites on affected versions should update now. Disclosed November 2026, reported by trangdld.

Vulnerability Overview

The PublishPress Revisions plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 4.3.0. This is due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with contributor-level access and above, to perform an unauthorized action.

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.

CWE-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in PublishPress Revisions <= 4.3.0 takes an account at Contributor level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For PublishPress Revisions the fix is 4.3.1: builds <= 4.3.0 are affected, anything from 4.3.1 onward is not.

Remediation

Update to version 4.3.1, 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: PublishPress Revisions 4.3.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-118187https://www.wordfence.com/threat-intel/vulnerabilities/id/1fb194ad-cbbb-4da7-9fd5-16dc429dfc83https://nvd.nist.gov/vuln/detail/CVE-2026-118187

Related records

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