PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes at a glance
- 9 publicly disclosed vulnerabilities, 2 of them rated High or Critical. The most recent was disclosed on Nov 20, 2026.
- Ranked #1609 by popularity on WordPress.org (10,000+ active installs).
- The latest version is 4.3.5 (released Nov 20, 2026). The most recent security fix shipped in 4.3.5.
- Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
- The first thing to do: update to the latest version and turn on automatic updates.
Check your PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes version
Enter the PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.
Your version number is compared on this page only. It is not sent anywhere.
Get an email when a new vulnerability is disclosed
We'll tell you when a new vulnerability is disclosed in “PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes”, with the version that fixes it. Free, email address only, stop any time.
We use your email address only for these alerts. Privacy policy
Want every plugin and theme on your site checked daily?
With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes”.
- 2
Compare it with the list below
If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.
- 3
Update
Click “Update now” to move to the latest version (4.3.5). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes vulnerabilities
PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes <= 4.3.4 - Missing Authorization to Authenticated (Contributor+) Arbitrary Post Deletion via 'pp_revisions_deleted' Parameter
Missing authorization · CVE-2026-123086
Affected versions: ≤ 4.3.4
Fixed in: 4.3.5
Severity: High 8.1 · Disclosed Nov 20, 2026
PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes <= 4.2.0 - Missing Authorization
Missing authorization · CVE-2026-120851
Affected versions: ≤ 4.2.0
Fixed in: 4.3.1
Severity: Medium 4.3 · Disclosed Nov 6, 2026
PublishPress Revisions <= 4.3.0 - Authenticated (Contributor+) Insecure Direct Object Reference
Missing authorization · CVE-2026-118187
Affected versions: ≤ 4.3.0
Fixed in: 4.3.1
Severity: Medium 4.3 · Disclosed Nov 4, 2026
PublishPress Revisions 3.9.0 - 4.2.0 - Authenticated (Subscriber+) Information Exposure
Information disclosure · CVE-2026-118188
Affected versions: ≥ 3.9.0, ≤ 4.2.0
Fixed in: 4.3.1
Severity: Medium 4.3 · Disclosed Nov 4, 2026
PublishPress Revisions 3.6.0 - 4.2.0 - Missing Authorization
Missing authorization · CVE-2026-118186
Affected versions: ≥ 3.6.0, ≤ 4.2.0
Fixed in: 4.3.1
Severity: Medium 4.3 · Disclosed Nov 4, 2026
PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes <= 3.7.23 - Unauthenticated SQL Injection
SQL injection · CVE-2026-32539
Affected versions: ≤ 3.7.23
Fixed in: 3.7.24
Severity: High 7.5 · Disclosed Mar 20, 2026
PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes <= 3.7.22 - Cross-Site Request Forgery
Cross-site request forgery (CSRF) · CVE-2026-25322
Affected versions: ≤ 3.7.22
Fixed in: 3.7.23
Severity: Medium 4.3 · Disclosed Jan 29, 2026
PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes <= 3.5.15 - Missing Authorization to Authenticated (Subscriber+) Sensitive Information Exposure
Missing authorization · CVE-2024-11154
Affected versions: ≤ 3.5.15
Fixed in: 3.5.16
Severity: Medium 4.3 · Disclosed Nov 19, 2024
PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes <= 3.5.14 - Reflected Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2024-9436
Affected versions: ≤ 3.5.14
Fixed in: 3.5.15
Severity: Medium 6.1 · Disclosed Oct 10, 2024
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes <= 4.3.4 - Missing Authorization to Authenticated (Contributor+) Arbitrary Post Deletion via 'pp_revisions_deleted' ParameterMissing authorization · CVE-2026-123086 | ≤ 4.3.4 | 4.3.5 | High 8.1 | Nov 20, 2026 |
| PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes <= 4.2.0 - Missing AuthorizationMissing authorization · CVE-2026-120851 | ≤ 4.2.0 | 4.3.1 | Medium 4.3 | Nov 6, 2026 |
| PublishPress Revisions <= 4.3.0 - Authenticated (Contributor+) Insecure Direct Object ReferenceMissing authorization · CVE-2026-118187 | ≤ 4.3.0 | 4.3.1 | Medium 4.3 | Nov 4, 2026 |
| PublishPress Revisions 3.9.0 - 4.2.0 - Authenticated (Subscriber+) Information ExposureInformation disclosure · CVE-2026-118188 | ≥ 3.9.0, ≤ 4.2.0 | 4.3.1 | Medium 4.3 | Nov 4, 2026 |
| PublishPress Revisions 3.6.0 - 4.2.0 - Missing AuthorizationMissing authorization · CVE-2026-118186 | ≥ 3.6.0, ≤ 4.2.0 | 4.3.1 | Medium 4.3 | Nov 4, 2026 |
| PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes <= 3.7.23 - Unauthenticated SQL InjectionSQL injection · CVE-2026-32539 | ≤ 3.7.23 | 3.7.24 | High 7.5 | Mar 20, 2026 |
| PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes <= 3.7.22 - Cross-Site Request ForgeryCross-site request forgery (CSRF) · CVE-2026-25322 | ≤ 3.7.22 | 3.7.23 | Medium 4.3 | Jan 29, 2026 |
| PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes <= 3.5.15 - Missing Authorization to Authenticated (Subscriber+) Sensitive Information ExposureMissing authorization · CVE-2024-11154 | ≤ 3.5.15 | 3.5.16 | Medium 4.3 | Nov 19, 2024 |
| PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes <= 3.5.14 - Reflected Cross-Site ScriptingCross-site scripting (XSS) · CVE-2024-9436 | ≤ 3.5.14 | 3.5.15 | Medium 6.1 | Oct 10, 2024 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Nov 20, 2026.
Most common weaknesses in PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes
Missing authorization
5 issues
Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.
Information disclosure
1 issue
Data that should stay private, such as user details or configuration values, can be read from outside.
SQL injection
1 issue
Input such as a form field can be used to rewrite the queries the site sends to its database. Attackers use it to pull out customer, member or order data.
Frequently asked questions
Is PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes safe to use?
PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes is a well-known plugin with 10,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (4.3.5) and turn on automatic updates.
How do I find which version of PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes my site is running?
In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.
Could updating break my site?
Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.
Can I check all my other plugins too?
Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.
Check every plugin and theme automatically, every day
Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.
Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.
← All plugin vulnerabilitiesPublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes on WordPress.org