File renaming via missing CSRF validation
Published Sep 17, 2024 · Updated Sep 17, 2024
Cross-site request forgery in Frog CMS 0.9.5 allows remote attackers to rename files through an authenticated administrator's browser. The file-manager rename action accepts attacker-chosen file[current_name] and file[new_name] POST fields and calls rename() without validating a CSRF token. Exploitation requires a logged-in user with file-manager permission to load attacker-controlled content, and the bounded consequence is renaming an existing CMS-managed file or directory.
Summary
What happened
Cross-site request forgery in Frog CMS 0.9.5 allows remote attackers to rename files through an authenticated administrator's browser. The file-manager rename action accepts attacker-chosen file[current_name] and file[new_name] POST fields and calls rename() without validating a CSRF token. Exploitation requires a logged-in user with file-manager permission to load attacker-controlled content, and the bounded consequence is renaming an existing CMS-managed file or directory.
The record
- CVE
- CVE-2024-46085
- Published
- Sep 17, 2024
- Updated
- Sep 17, 2024
- Vendor
- Frog CMS Project
- Product
- Frog CMS
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 17, 2024CVE publishedPublication date reported by the CVE source.
- Sep 17, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.9.5
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