Authenticated code execution via dangerous .phar upload
Published Dec 19, 2025 · Updated Dec 19, 2025
Unrestricted file upload in Dotclear 2.25.3 allows remote authenticated users to execute arbitrary PHP via a crafted .phar file. The blog post creation interface accepts a .phar upload into the public media path without blocking its executable file type. Access to a post-authoring account is required, and requesting the uploaded file causes the web server to run its PHP payload.
Summary
What happened
Unrestricted file upload in Dotclear 2.25.3 allows remote authenticated users to execute arbitrary PHP via a crafted .phar file. The blog post creation interface accepts a .phar upload into the public media path without blocking its executable file type. Access to a post-authoring account is required, and requesting the uploaded file causes the web server to run its PHP payload.
The record
- CVE
- CVE-2023-53952
- Published
- Dec 19, 2025
- Updated
- Dec 19, 2025
- Vendor
- Dotclear
- Product
- Dotclear
- Classifications
- CWE-434, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 19, 2025CVE publishedPublication date reported by the CVE source.
- Dec 19, 2025Record 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=2.25.3
What conditions does exploitation require?
What is affected?
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
- dotclear 2.25.3 authenticated RCE via file uploadfunctional · validated
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