CVE-2026-118188 · Package
NO FIX YET · SEE WHAT TO DO
The PublishPress Revisions WordPress plugin before 4.3.1 does not check whether a user may read a post when returning revision comparisons. Any logged-in user, including a Subscriber, can read the title, content and excerpt of other users' private, draft, pending, scheduled or trashed posts.
first public Nov 6, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running the PublishPress Revisions plugin before 4.3.1 where any logged-in account, including low-privilege subscribers, can exist. The flaw exposes unpublished content of other users through the revision-comparison feature. Sites without this plugin, or with it already at 4.3.1 or later, are not affected.
Not affected if no-untrusted-accounts, plugin-at-4.3.1-or-later, plugin-not-installed
Who cares publishpress-revisions, self-hosted, wordpress
wp plugin get revisionary --field=version4.3.1 or laterThe PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes WordPress plugin before 4.3.1 does not verify that a user is permitted to read a given post before returning its content through its revision-comparison feature, allowing any authenticated user, including a Subscriber, to read the title, content and excerpt of any other user's private, draft, pending, scheduled or trashed post.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.