Subscriber content modification via permissive role defaults
Published Apr 5, 2021 · Updated Aug 3, 2024
Incorrect authorization in Themeum WP Page Builder before 1.2.4 allows remote authenticated users to modify or delete posts and pages. The role-exclusion setting permits every role by default, so a subscriber can open a post editor URL with action=wppb_editor and publish changes. Any logged-in subscriber or customer account is sufficient; the flaw changes site content but does not itself provide code execution.
Summary
What happened
Incorrect authorization in Themeum WP Page Builder before 1.2.4 allows remote authenticated users to modify or delete posts and pages. The role-exclusion setting permits every role by default, so a subscriber can open a post editor URL with action=wppb_editor and publish changes. Any logged-in subscriber or customer account is sufficient; the flaw changes site content but does not itself provide code execution.
The record
- CVE
- CVE-2021-24207
- Published
- Apr 5, 2021
- Updated
- Aug 3, 2024
- Vendor
- Themeum
- Product
- WP Page Builder
- Classifications
- CWE-863, CWE-269
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 5, 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=1.2.4 <1.2.4
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.
Public exploit references
- WPScan subscriber editor URL proof of conceptfunctional · validated
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