Privileged-action forgery via REST auth check
Published Aug 18, 2026 · Updated Aug 19, 2026
Cross-site request forgery in DevItems HashBar before 2.0.1 allows attackers to submit forged tracking requests via a victim admin session. The 2.0.1 changelog states that analytics and tracking REST endpoints used an authentication check that permitted request-forgery bypasses instead of rejecting requests without a valid anti-CSRF proof, and no public diff names the exact route. Exploitation requires a logged-in WordPress administrator or other privileged user to load attacker-controlled content, after which the forged request runs with that user’s session and can alter whatever tracking action the endpoint exposes.
Summary
What happened
Cross-site request forgery in DevItems HashBar before 2.0.1 allows attackers to submit forged tracking requests via a victim admin session. The 2.0.1 changelog states that analytics and tracking REST endpoints used an authentication check that permitted request-forgery bypasses instead of rejecting requests without a valid anti-CSRF proof, and no public diff names the exact route. Exploitation requires a logged-in WordPress administrator or other privileged user to load attacker-controlled content, after which the forged request runs with that user’s session and can alter whatever tracking action the endpoint exposes.
The record
- CVE
- CVE-2026-66602
- Published
- Aug 18, 2026
- Updated
- Aug 19, 2026
- Vendor
- DevItems
- Product
- HashBar
- Classifications
- CWE-352, CAPEC-62
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 18, 2026CVE publishedPublication date reported by the CVE source.
- Aug 19, 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=n/a <=2.0.0 changes=[{"at":"2.0.1","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