CVE-2026-116009 — Camaleon CMS before 2.9.3 Path Traversal RCE via Media crop_url Action
Camaleon CMS before 2.9.3 contains a path traversal vulnerability that allows users with only the media permission to write arbitrary files by supplying ../ sequences in the name parameter. Attackers can send a base64 data: URI to the crop_url media action to write an ERB template into a theme's views directory, which executes when rendered.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.4% (30-day exploitation probability)+5
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Owen2345 Camaleon CMS).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (file handling), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Owen2345 | Camaleon CMS | < 2.9.3 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 8.7 | CVSS 4.0 | High | — | — | disclosure@vulncheck.com via NIST National Vulnerability Database |
| 8.7 | CVSS 4.0 | High | — | — | VulnCheck via CVE Program (cve.org) e CISA ADP |
| 8.8 | CVSS 3.1 | High | 2.8 | 5.9 | disclosure@vulncheck.com via NIST National Vulnerability Database |
| 8.8 | CVSS 3.1 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
| 8.8 | CVSS 3.1 | High | — | — | VulnCheck via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: disclosure@vulncheck.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 25, 2026 → Oct 29, 2026 · 5 reading(s) · max 0.42%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Monitor file creation in web directories and paths with traversal sequences (../).
Timeline
What happened to this CVE, newest first.
- 2026
- SSVC assessment updated
- Source status changed · Received → Deferred
- Affected products added · owen2345/camaleon-cms
- Record published
- CVSS changed · 8.8
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 24, 2026 – Oct 26, 2026
- 1× Official description updated · Oct 24, 2026 – Oct 24, 2026
References
9 on the record
- github.com/owen2345/camaleon-cms/commit/430cce27ea63a397a7b7fa0260b4ec2128ea63fd
- github.com/owen2345/camaleon-cms/pull/1201
- github.com/owen2345/camaleon-cms/pull/1211
- www.vulncheck.com/advisories/camaleon-cms-before-2.9.3-path-traversal-rce-via-media-cro
- nvd.nist.gov/vuln/detail/CVE-2026-116009
- github.com/advisories/GHSA-wq77-q3hj-c75x
- github.com/owen2345/camaleon-cms/releases/tag/2.9.3
- github.com/owen2345/camaleon-cms/blob/2.9.2/app/helpers/camaleon_cms/uploader_he
- gist.github.com/lukmanazri/b7e76a1ddc84dc977800013c53f671b5
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-102261 owen2345 Camaleon CMS Media Crop media_controller.rb crop authorization Sep 29, 2026
- Medium CVE-2026-86100 Camaleon CMS 2.7.5 through 2.9.1 SSRF via HTTP Redirect in Upload from URL Sep 4, 2026
- High CVE-2026-73329 CamaleonCMS Stored XSS via Draft Post Title Creation Endpoint Aug 12, 2026
- Medium CVE-2026-73330 CamaleonCMS 2.9.1 Server-Side Template Injection via test_email Action Aug 12, 2026
- High CVE-2026-73331 CamaleonCMS 2.9.1 Authenticated SQL Injection via Post Slug Field Aug 12, 2026
- High CVE-2026-73332 CamaleonCMS cama_contact_form Plugin Stored XSS via before_html Field Aug 12, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-116009 is "Camaleon CMS before 2.9.3 Path Traversal RCE via Media crop_url Action", rated High. It affects Camaleon CMS (Owen2345); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.8 describes technical severity. EPSS 0.42% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.