Subscriber-level post-content modification via unchecked AJAX write
Published Sep 27, 2021 · Updated Aug 3, 2024
Missing authorization in WPDeveloper Countdown Block before 1.1.2 allows remote authenticated users to alter displayed post content. The eb_write_block_css AJAX action accepts a post ID and attacker-controlled CSS data without checking whether the caller may edit that post, then persists styles that change its rendered content. Subscriber-level access is sufficient, and the demonstrated consequence is persistent alteration of the selected post's visible presentation.
Summary
What happened
Missing authorization in WPDeveloper Countdown Block before 1.1.2 allows remote authenticated users to alter displayed post content. The eb_write_block_css AJAX action accepts a post ID and attacker-controlled CSS data without checking whether the caller may edit that post, then persists styles that change its rendered content. Subscriber-level access is sufficient, and the demonstrated consequence is persistent alteration of the selected post's visible presentation.
The record
- CVE
- CVE-2021-24633
- Published
- Sep 27, 2021
- Updated
- Aug 3, 2024
- Vendor
- WPDeveloper
- Product
- Countdown Block
- Classifications
- CWE-862, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 27, 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.1.2 <1.1.2
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 authenticated AJAX proof of conceptproof of concept · demonstrated
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