Camaleon CMS vulnerable to remote code execution through code injection (GHSL-2024-185)
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (camaleon_cms 2.8.1), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
RubyGems camaleon_cms
- Affected
- < 2.8.1
- Fixed in
- 2.8.1
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-7x4w-cj9r-h4v9 lists affected ranges: RubyGems camaleon_cms >=0 <2.8.1
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 8.6 · 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 · score source
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
The actions defined inside of the MediaController class do not check whether a given path is inside a certain path (e.g. inside the media folder). If an attacker performed an account takeover of an administrator account (See: GHSL-2024-184) they could delete arbitrary files or folders on the server hosting Camaleon CMS. The cropurl action might make arbitrary file writes (similar impact to GHSL-2024-182) for any authenticated user possible, but it doesn't seem to work currently. Arbitrary file deletion can be exploited with following code path: The parameter folder flows from the actions method: into the method deletefile of the CamaleonCmsLocalUploader class (when files are uploaded locally): Where it is joined in an unchecked manner with the root folder and then deleted. Proof of concept The following request would delete the file README.md in the top folder of the Ruby on Rails application. (The values for authtoken, X-CSRF-Token and cmssession would also need to be replaced with…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-7x4w-cj9r-h4v9
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-7x4w-cj9r-h4v9 Advisory: Camaleon CMS vulnerable to remote code execution through code injection (GHSL-2024-185) IDs: GHSA-7x4w-cj9r-h4v9 Record: https://patchnext.com/advisories/ghsa-7x4w-cj9r-h4v9 (revision 1, source checked 26 Oct 2026, 15:49 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 8.6) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: camaleon_cms 2.8.1. A vendor fix does not mean a deployment is fixed. ## Affected components - RubyGems camaleon_cms: affected < 2.8.1; fixed in 2.8.1 ## Suggested inspection (read-only) - RubyGems camaleon_cms: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on camaleon_cms. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-7x4w-cj9r-h4v9 (GitHub-reviewed advisory GHSA-7x4w-cj9r-h4v9 lists affected ranges: RubyGems camaleon_cms >=0 <2.8.1) Commands are suggestions: review each one before running it.
Loading voting…