CVE-2026-110468: WidzialniCMS: unauthenticated file upload leads to RCE
CRITICALWidzialniCMS has an unrestricted file upload flaw in /panel/controllers/save_photo.php (CWE-434). The permission check is controlled by the client and the currentpath parameter is poorly validated, so an unauthenticated attacker can write arbitrary files anywhere on the server and get remote code execution. This is a generic CMS flaw rather than an AI/ML component, so it only matters if the CMS fronts or sits next to ML dashboards, model documentation portals or other AI-related web assets on the same host. No CVSS score, EPSS data, KEV listing, public exploit or Nuclei template exists yet, so the likelihood of exploitation is unquantified. The bug is trivial to abuse, though, and the vendor-fixed release is public, which makes reverse-engineering the patch easy. Upgrade to version 2.5 now, and check the host for unexpected files in upload and web-accessible directories.
What is the risk?
Critical severity by the source rating, but no CVSS vector, EPSS score, KEV listing or public exploit is available, so exploitation likelihood is unquantified. Unauthenticated network access, arbitrary file write and resulting code execution make the technical risk high for any internet-exposed instance. Relevance to AI/ML systems is incidental: the product is a general-purpose CMS, with no tracked AI package or dependents data. Risk is highest where the web server shares a host, credentials or network segments with ML infrastructure.
How does the attack unfold?
What systems are affected?
| Package | Ecosystem | Vulnerable Range | Patched |
|---|---|---|---|
| WidzialniCMS | — | — | No patch |
Do you use WidzialniCMS? You're affected.
How severe is it?
What should I do?
1 step1) Upgrade WidzialniCMS to version 2.5 or later. 2) If patching is delayed, block access to /panel/controllers/save_photo.php with a WAF or reverse-proxy rule, or restrict /panel/ to trusted IPs. 3) Disable script execution (PHP and similar) in upload directories. 4) Search web roots for recently created or modified executable files (.php, .phtml, .phar) and review web logs for POST requests to save_photo.php from unauthenticated sessions, especially with unusual currentpath values such as traversal sequences. 5) Rotate any credentials or API keys stored on the host if compromise is suspected. 6) Isolate the CMS from AI/ML infrastructure through network segmentation. 7) Follow the CERT.pl advisory for further guidance.
How is it classified?
Which compliance frameworks are affected?
This CVE is relevant to:
Frequently Asked Questions
What is CVE-2026-110468?
WidzialniCMS has an unrestricted file upload flaw in /panel/controllers/save_photo.php (CWE-434). The permission check is controlled by the client and the currentpath parameter is poorly validated, so an unauthenticated attacker can write arbitrary files anywhere on the server and get remote code execution. This is a generic CMS flaw rather than an AI/ML component, so it only matters if the CMS fronts or sits next to ML dashboards, model documentation portals or other AI-related web assets on the same host. No CVSS score, EPSS data, KEV listing, public exploit or Nuclei template exists yet, so the likelihood of exploitation is unquantified. The bug is trivial to abuse, though, and the vendor-fixed release is public, which makes reverse-engineering the patch easy. Upgrade to version 2.5 now, and check the host for unexpected files in upload and web-accessible directories.
Is CVE-2026-110468 actively exploited?
No confirmed active exploitation of CVE-2026-110468 has been reported, but organizations should still patch proactively.
How to fix CVE-2026-110468?
1) Upgrade WidzialniCMS to version 2.5 or later. 2) If patching is delayed, block access to /panel/controllers/save_photo.php with a WAF or reverse-proxy rule, or restrict /panel/ to trusted IPs. 3) Disable script execution (PHP and similar) in upload directories. 4) Search web roots for recently created or modified executable files (.php, .phtml, .phar) and review web logs for POST requests to save_photo.php from unauthenticated sessions, especially with unusual currentpath values such as traversal sequences. 5) Rotate any credentials or API keys stored on the host if compromise is suspected. 6) Isolate the CMS from AI/ML infrastructure through network segmentation. 7) Follow the CERT.pl advisory for further guidance.
What systems are affected by CVE-2026-110468?
This vulnerability affects the following AI/ML architecture patterns: Web content management systems, Internet-facing web applications, Hosts shared with ML dashboards or documentation portals.
What is the CVSS score for CVE-2026-110468?
No CVSS score has been assigned yet.
What is the AI security impact?
Affected AI Architectures
MITRE ATLAS Techniques
AML.T0049Exploit Public-Facing ApplicationCompliance Controls Affected
What are the technical details?
Original Advisory
WidzialniCMS is vulnerable to Unrestricted File Upload in the /panel/controllers/save_photo.php endpoint. Due to a client-controlled permission check parameter and insufficient validation of the currentpath parameter, an unauthenticated attacker can upload arbitrary files to any locations on the server, leading to Remote Code Execution. This issue has been fixed in version 2.5.
Exploitation Scenario
An attacker finds an internet-facing WidzialniCMS instance, for example through a Shodan or Censys fingerprint. They send a crafted multipart POST request to /panel/controllers/save_photo.php, manipulating the client-side permission parameter to bypass authorization and setting currentpath to a web-accessible directory. The uploaded PHP web shell then gives them code execution as the web server user. From there they read configuration files and environment variables, steal any LLM API keys or database credentials stored on the host, and attempt lateral movement towards internal ML or data services reachable from the server.
Weaknesses (CWE)
CWE-434 — Unrestricted Upload of File with Dangerous Type: The product allows the upload or transfer of dangerous file types that are automatically processed within its environment.
- [Architecture and Design] Generate a new, unique filename for an uploaded file instead of using the user-supplied filename, so that no external input is used at all.[REF-422] [REF-423]
- [Architecture and Design] When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
Source: MITRE CWE corpus.
References
- cert.pl/posts/2026/11/CVE-2026-110468third-party-advisory
- widzialni.org/funkcjonalnosci-widzialni-cms,sd,mg,0,175product
Timeline
Related Vulnerabilities
CVE-2025-512010.0smolagents: sandbox escape enables unauthenticated RCE
Same attack type: Code ExecutionCVE-2025-5952810.0Flowise: Unauthenticated RCE via MCP config injection
Same attack type: Code ExecutionCVE-2025-282810.0LangChain RequestsToolkit: SSRF exposes cloud metadata
Same attack type: Auth BypassCVE-2025-5376710.0Azure OpenAI: SSRF EoP, no auth required (CVSS 10)
Same attack type: Auth BypassCVE-2024-291210.0BentoML: RCE via insecure deserialization (CVSS 10)
Same attack type: Code Execution