CVE-2026-118186

PublishPress Revisions 3.6.0 - 4.2.0 - Missing Authorization

2026-11-04 00:00

Strategic Overview

Status: Patched in 4.3.1
Affected Plugin: PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes
Affected Version: 3.6.0 – 4.2.0
CVSS: 4.3Medium
Weakness type: CWE-863 · Incorrect Authorization
CVE: CVE-2026-118186

View all PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes vulnerabilities

At a glance

CVE-2026-118186 is a medium-severity Incorrect Authorization vulnerability in the PublishPress Revisions WordPress plugin, affecting versions 3.6.0 – 4.2.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. 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 unauthorized access in versions 3.6.0 through 4.2.0. This is due to a missing capability check on a function. 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-863: Incorrect Authorization

Reaching this weakness in PublishPress Revisions 3.6.0 – 4.2.0 takes a caller who can reach the endpoint. Incorrect authorization means a permission check exists but evaluates the wrong thing, so it passes for callers it was meant to stop.

The action runs for users the code intended to exclude, with the same effect as having no check at all. For PublishPress Revisions the fix is 4.3.1: builds 3.6.0 – 4.2.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-118186 https://www.wordfence.com/threat-intel/vulnerabilities/id/d05c58df-8b13-413e-babb-dee87ac17b4e https://nvd.nist.gov/vuln/detail/CVE-2026-118186

Related records

Other vulnerabilities in PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes

CVSS Vector

4.3

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged
ConfidentialityNone
IntegrityLow
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/