Authenticated code execution via dangerous file upload
Published Dec 24, 2025 · Updated Dec 24, 2025
Unrestricted file upload in EchoCCS Specto CM before 17032025 allows remote authenticated users to execute uploaded server-side code. The Turkish CNA identifies dangerous-file upload leading to remote code inclusion but does not disclose the affected endpoint, upload field, validation failure, or execution path. Low-privileged authenticated access is required; successful exploitation executes attacker-supplied code within the affected Specto CM deployment.
Summary
What happened
Unrestricted file upload in EchoCCS Specto CM before 17032025 allows remote authenticated users to execute uploaded server-side code. The Turkish CNA identifies dangerous-file upload leading to remote code inclusion but does not disclose the affected endpoint, upload field, validation failure, or execution path. Low-privileged authenticated access is required; successful exploitation executes attacker-supplied code within the affected Specto CM deployment.
The record
- CVE
- CVE-2025-2155
- Published
- Dec 24, 2025
- Updated
- Dec 24, 2025
- Vendor
- EchoCCS
- Product
- Specto CM
- Classifications
- CWE-434, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 24, 2025CVE publishedPublication date reported by the CVE source.
- Dec 24, 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=0 <17032025
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