Camaleon CMS vulnerable to stored XSS through user file upload (GHSL-2024-184)

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

4.8 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

A stored cross-site scripting has been found in the image upload functionality that can be used by normal registered users: It is possible to upload a SVG image containing JavaScript and it's also possible to upload a HTML document when the format parameter is manually changed to documents or a string of an unsupported format. If an authenticated user or administrator visits that uploaded image or document malicious JavaScript can be executed on their behalf (e.g. changing or deleting content inside of the CMS.) Proof of concept Login as a normal user (if user signup is enabled). Go to the user's profile. And upload the following profile picture via drag and drop. The content of the SVG file could be as follows (e.g. name it test-xss.svg): <?xml version="1.0" encoding="UTF-8" standalone="no"? <svg xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://creativecommons.org/ns#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:svg="http://www.w3.org/2000/svg"…

Published by the source

18 Sep 2024, 15:47 UTC

Last modified by the source

18 Sep 2024, 15:47 UTC

Source last checked

26 Oct 2026, 15:48 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-r9cr-qmfw-pmrc

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-r9cr-qmfw-pmrc

Advisory: Camaleon CMS vulnerable to stored XSS through user file upload (GHSL-2024-184)
IDs: GHSA-r9cr-qmfw-pmrc
Record: https://patchnext.com/advisories/ghsa-r9cr-qmfw-pmrc (revision 1, source checked 26 Oct 2026, 15:48 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.8)
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-r9cr-qmfw-pmrc (GitHub-reviewed advisory GHSA-r9cr-qmfw-pmrc lists affected ranges: RubyGems camaleon_cms >=0 <2.8.1)

Commands are suggestions: review each one before running it.