Unauthenticated arbitrary file deletion
Published Apr 10, 2022 · Updated Aug 3, 2024
Arbitrary file deletion in zbzcms 1.0 allows remote attackers to delete server files through the /include/up.php endpoint. The public CVE record and its unavailable report do not disclose which request parameter reaches a filesystem deletion operation or how the path is validated. No authentication or user interaction is required, and deletion of application or server files can corrupt content or interrupt the service.
Summary
What happened
Arbitrary file deletion in zbzcms 1.0 allows remote attackers to delete server files through the /include/up.php endpoint. The public CVE record and its unavailable report do not disclose which request parameter reaches a filesystem deletion operation or how the path is validated. No authentication or user interaction is required, and deletion of application or server files can corrupt content or interrupt the service.
The record
- CVE
- CVE-2022-27133
- Published
- Apr 10, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1485
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 10, 2022CVE 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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