Authenticated PHP execution via unsanitized post title
Published Jun 3, 2021 · Updated Aug 4, 2024
Arbitrary file write in SomeBottle OBottle 2.0 allows remote authenticated users to execute PHP through a crafted post title. The c/t.php publishing handler accepts PHP syntax in the title and writes it into a generated post without neutralizing executable code. Access to the administrative publishing interface is required, and successful exploitation runs attacker-supplied PHP in the web server context.
Summary
What happened
Arbitrary file write in SomeBottle OBottle 2.0 allows remote authenticated users to execute PHP through a crafted post title. The c/t.php publishing handler accepts PHP syntax in the title and writes it into a generated post without neutralizing executable code. Access to the administrative publishing interface is required, and successful exploitation runs attacker-supplied PHP in the web server context.
The record
- CVE
- CVE-2020-36008
- Published
- Jun 3, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 3, 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
- Authenticated crafted-title PHP payloadproof 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