GHSA-75j2-9gmc-m855: Camaleon CMS vulnerable to stored XSS through user file upload (GHSL-2024-184)
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][1] or a string of an [unsupported format][2].
Published Sep 25, 2024
Affected packages
camaleon_cms
- Ecosystem
- RubyGems
- Affected
- >= 2.8.0, < 2.8.2
- Fixed in
- 2.8.2
- Check
bundle info camaleon_cms
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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][1] or a string of an [unsupported format][2]. 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.)
[1]: https://github.com/owen2345/camaleon-cms/blob/feccb96e542319ed608acd3a16fa5d92f13ede67/app/uploaders/camaleon_cms_uploader.rb#L105-L106 [2]: https://github.com/owen2345/camaleon-cms/blob/feccb96e542319ed608acd3a16fa5d92f13ede67/app/uploaders/camaleon_cms_uploader.rb#L110-L111
Impact
This issue may lead to account takeover due to reflected Cross-site scripting (XSS).
Remediation
Only allow the upload of safe files such as PNG, TXT and others or serve all "unsafe" files such as SVG and other files with a content-disposition: attachment header, which should prevent browsers from displaying them.
Additionally, a [Content security policy (CSP)][3] can be created that disallows inlined script. (Other parts of the application might need modification to continue functioning.)
[3]: https://web.dev/articles/csp
To prevent the theft of the auth_token it could be marked with HttpOnly. This would however not prevent that actions could be performed as the authenticated user/administrator. Furthermore, it could make sense to use the authentication provided by Ruby on Rails, so that stolen tokens cannot be used anymore after some time.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More RubyGems vulnerabilities
All RubyGems entriesCVE-2026-1776
Camaleon CMS vulnerable to Path Traversal through AWS S3 uploader implementation
medium6.5No fixMar 10, 2026CVE-2025-2304
Camaleon CMS Vulnerable to Privilege Escalation through a Mass Assignment
critical9.4Mar 14, 2025CVE-2024-48652
camaleon_cms affected by cross site scripting
medium4.8No fixOct 23, 2024GHSA-8fx8-3rg2-79xw
Camaleon CMS vulnerable to stored XSS through user file upload (GHSL-2024-184)
medium5.4Sep 23, 2024CVE-2024-46986
Camaleon CMS affected by arbitrary file write to RCE (GHSL-2024-182)
high8.8Sep 18, 2024CVE-2024-46987
Camaleon CMS vulnerable to arbitrary path traversal (GHSL-2024-183)
high6.5Sep 18, 2024
