Unauthorized cache clearing via forged administrator requests
Published Dec 31, 2022 · Updated Apr 9, 2025
Cross-site request forgery in Froxlor before 2.0.0-beta1 allows remote attackers to clear APCu or reset OPcache through an administrator. The admin_apcuinfo.php and admin_opcacheinfo.php handlers execute apcu_clear_cache() or opcache_reset() from an action parameter without requiring a POST confirmation. An administrator with server-settings permission must remain authenticated and load attacker-controlled content, after which cached PHP data or bytecode is invalidated.
Summary
What happened
Cross-site request forgery in Froxlor before 2.0.0-beta1 allows remote attackers to clear APCu or reset OPcache through an administrator. The admin_apcuinfo.php and admin_opcacheinfo.php handlers execute apcu_clear_cache() or opcache_reset() from an action parameter without requiring a POST confirmation. An administrator with server-settings permission must remain authenticated and load attacker-controlled content, after which cached PHP data or bytecode is invalidated.
The record
- CVE
- CVE-2022-4867
- Published
- Dec 31, 2022
- Updated
- Apr 9, 2025
- Vendor
- Froxlor
- Product
- Froxlor
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 31, 2022CVE publishedPublication date reported by the CVE source.
- Apr 9, 2025Record 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=unspecified <2.0.0-beta1
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