Page deletion via forged administrative request
Published Mar 10, 2021 · Updated Aug 4, 2024
Cross-site request forgery in FUEL CMS 1.4.13 allows remote attackers to delete pages through the administrative delete endpoint. The Module::delete method accepts a page identifier from a POST request at /pages/delete/{id}, then passes that identifier into the page-deletion path. Exploitation requires an authenticated user's browser to submit the crafted request, and the bounded consequence is deletion of CMS pages.
Summary
What happened
Cross-site request forgery in FUEL CMS 1.4.13 allows remote attackers to delete pages through the administrative delete endpoint. The Module::delete method accepts a page identifier from a POST request at /pages/delete/{id}, then passes that identifier into the page-deletion path. Exploitation requires an authenticated user's browser to submit the crafted request, and the bounded consequence is deletion of CMS pages.
The record
- CVE
- CVE-2020-28705
- Published
- Mar 10, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-352, CAPEC-62, T1485
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 10, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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
- FUEL CMS page-deletion CSRF proof of conceptproof of concept · unverified
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