Unauthenticated code execution via arbitrary file upload
Published Aug 4, 2025 · Updated Jul 5, 2026
Arbitrary file upload in ZKEACMS 4.1 allows remote attackers to execute arbitrary code by submitting a crafted file. Published records do not identify the upload endpoint or specify which server-side filename, extension, MIME-type, or content check fails. No privileges or user interaction are required; a successful upload runs attacker-supplied code in the server process context.
Summary
What happened
Arbitrary file upload in ZKEACMS 4.1 allows remote attackers to execute arbitrary code by submitting a crafted file. Published records do not identify the upload endpoint or specify which server-side filename, extension, MIME-type, or content check fails. No privileges or user interaction are required; a successful upload runs attacker-supplied code in the server process context.
The record
- CVE
- CVE-2025-52239
- Published
- Aug 4, 2025
- Updated
- Jul 5, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-434, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 4, 2025CVE publishedPublication date reported by the CVE source.
- Jul 5, 2026Record 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.
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