Forced privileged-user actions via forged requests
Published Apr 26, 2024 · Updated Apr 28, 2026
Cross-site request forgery in ClickCease Click Fraud Protection 3.2.7 and earlier allows remote attackers to trigger unwanted actions. Neither Patchstack nor the CNA record identifies the affected request handler or state-changing operation, leaving the exact missing CSRF validation undisclosed. Exploitation requires a privileged WordPress user to visit a crafted page or submit a malicious form, after which actions run under that user's session.
Summary
What happened
Cross-site request forgery in ClickCease Click Fraud Protection 3.2.7 and earlier allows remote attackers to trigger unwanted actions. Neither Patchstack nor the CNA record identifies the affected request handler or state-changing operation, leaving the exact missing CSRF validation undisclosed. Exploitation requires a privileged WordPress user to visit a crafted page or submit a malicious form, after which actions run under that user's session.
The record
- CVE
- CVE-2024-33678
- Published
- Apr 26, 2024
- Updated
- Apr 28, 2026
- Vendor
- CHEQ
- Product
- ClickCease
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 26, 2024CVE publishedPublication date reported by the CVE source.
- Apr 28, 2026Record 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=0 <=3.2.4
- Affected versionversion=0 <=3.2.7 changes=[{"at":"3.2.8","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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