Authenticated arbitrary file write via tp.php
Published May 11, 2022 · Updated Aug 3, 2024
Arbitrary file write in ftcms 2.1 and earlier allows remote authenticated users to write server-side files through admin/controllers/tp.php. The public record identifies the controller but does not disclose which input reaches the file-system write or how path and content controls fail. An authenticated session is required; successful writes can alter server-side application data, while code execution is not established.
Summary
What happened
Arbitrary file write in ftcms 2.1 and earlier allows remote authenticated users to write server-side files through admin/controllers/tp.php. The public record identifies the controller but does not disclose which input reaches the file-system write or how path and content controls fail. An authenticated session is required; successful writes can alter server-side application data, while code execution is not established.
The record
- CVE
- CVE-2022-30060
- Published
- May 11, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 11, 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