Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Network-reachable upload feature (AV:N/AC:L) but highest admin privilege required (PR:H); no scope change as impact is confined to the vulnerable system.
Primary rating from Vendor (jpcert).
CVSS VectorVendor: jpcert
Lifecycle Timeline
5DescriptionCVE.org
freo2 provided by refirio contains an unrestricted upload of file with dangerous type vulnerability. A user with the highest-level administrative privileges for the product may upload an executable file and execute arbitrary OS commands.
AnalysisAI
Unrestricted file upload in freo2 (by refirio) versions prior to 2.0.0-alpha-14 enables highest-privilege administrative users to upload executable files and trigger arbitrary OS command execution on the underlying server. Reported by JPCERT and covered under JVN#52865575, this is a post-authentication code execution path requiring no user interaction once admin access is established. No public exploit code or CISA KEV listing has been identified at time of analysis.
Technical ContextAI
freo2 is a PHP-based CMS developed by refirio, identified via CPE cpe:2.3:a:refirio:freo2:*:*:*:*:*:*:*:*. The root cause is CWE-434 (Unrestricted Upload of File with Dangerous Type), a class of vulnerability where the application fails to adequately validate or restrict the MIME type, extension, or content of uploaded files. In practice, this typically means an attacker can upload a server-side executable (e.g., a PHP webshell) through the CMS file manager, which is then stored in a web-accessible directory and can be directly invoked via HTTP request, causing the web server to execute the embedded code with the application's runtime privileges.
RemediationAI
Upgrade to freo2 version 2.0.0-alpha-14 or later, which resolves the unrestricted file upload vulnerability per the JPCERT/JVN advisory at https://jvn.jp/en/jp/JVN52865575/. The upstream fix can be reviewed in the commit history at https://github.com/refirio/freo2/commits/main/; note that the referenced fix is via commits rather than a formally tagged stable release, so operators should verify the exact commit that introduces the restriction before upgrading in production. If immediate upgrade is not possible, a compensating control is to restrict the file upload functionality at the web server level - for example, configure the web server to deny execution of scripts (PHP, CGI, etc.) in the upload storage directory, and audit existing uploaded files for executable content. This workaround reduces exploitation impact but does not eliminate the upload path itself.
Same technique File Upload
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-52636
GHSA-3w4q-685g-qf2v