Contributor privilege escalation via unchecked deletion scheduling
Published Nov 8, 2021 · Updated Aug 3, 2024
Incorrect authorization in PublishPress Future before 2.6.0 allows remote authenticated users to schedule deletion of arbitrary posts. The plugin’s post-expiration scheduling path accepts Contributor-level requests without enforcing the required capability before recording deletion actions for posts outside that role’s authority. Access requires an authenticated WordPress account with at least the Contributor role; successful abuse alters post integrity by causing arbitrary posts to be deleted when scheduled.
Summary
What happened
Incorrect authorization in PublishPress Future before 2.6.0 allows remote authenticated users to schedule deletion of arbitrary posts. The plugin’s post-expiration scheduling path accepts Contributor-level requests without enforcing the required capability before recording deletion actions for posts outside that role’s authority. Access requires an authenticated WordPress account with at least the Contributor role; successful abuse alters post integrity by causing arbitrary posts to be deleted when scheduled.
The record
- CVE
- CVE-2021-24783
- Published
- Nov 8, 2021
- Updated
- Aug 3, 2024
- Vendor
- PublishPress
- Product
- PublishPress Future
- Classifications
- CWE-863, T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 8, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.6.0 <2.6.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo