{"answers":{"affected":"2 open source packages ship an affected version, including camaleon_cms. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-18260 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-18260 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-18260 is a medium-severity cross-site scripting vulnerability in n/a, published on 15 Oct 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-18260 and fix it if it is affected.\n\nWhat it is: CVE-2018-18260 is a medium-severity cross-site scripting vulnerability in n/a, published on 15 Oct 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-18260 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- camaleon_cms (RubyGems): affected all versions; no fix listed\n- camaleon_cms (RubyGems): affected all versions; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2018-18260/ (Markdown: https://insights.sbomify.com/CVE-2018-18260/index.md)","id":"CVE-2018-18260","markdown":"https://insights.sbomify.com/CVE-2018-18260/index.md","name":"CVE-2018-18260","record":{"aliases":["GHSA-7f84-9cqf-g4j9"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Camaleon CMS","requires_auth":"none","summary":"Stored XSS in Camaleon CMS allows attackers to execute scripts via profile image uploads, though the vendor disputes reproducibility.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"camaleon_cms","vendor":"tuzitio"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"In the 2.4 version of Camaleon CMS, Stored XSS has been discovered. The profile image in the User settings section can be run in the update / upload area via /admin/media/upload?actions=false. NOTE: the vendor reports that they are \"unable to reproduce the reported issue on any version.\"","ecosystems":["RubyGems"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Camaleon CMS vulnerable to Stored Cross-site Scripting","id":"CVE-2018-18260","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"xss","year":"2018"},"n_packages":2,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-18261"},"packages":[{"ecosystem":"RubyGems","fixed":[],"introduced":[],"last_affected":[],"package":"camaleon_cms","purl":null,"source":"GHSA-7f84-9cqf-g4j9"},{"ecosystem":"RubyGems","fixed":[],"introduced":[],"last_affected":[],"package":"camaleon_cms","purl":"pkg:gem/camaleon_cms","source":"GHSA-7f84-9cqf-g4j9"}],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-18259"},"products":["n/a"],"published":"2018-10-15","related":[{"cvss_score":10,"headline":"Arbitrary file write leading to RCE in Camaleon CMS","id":"CVE-2024-46986","kev_date_added":null,"published":"2024-09-18"},{"cvss_score":9.8,"headline":"Server-Side Template Injection in Camaleon CMS","id":"CVE-2023-30145","kev_date_added":null,"published":"2023-05-26"},{"cvss_score":8.8,"headline":"Camaleon CMS - Insufficient Session Expiration after Password Change","id":"CVE-2021-25970","kev_date_added":null,"published":"2021-10-20"},{"cvss_score":7.7,"headline":"Arbitrary path traversal in Camaleon CMS","id":"CVE-2024-46987","kev_date_added":null,"published":"2024-09-18"},{"cvss_score":6.1,"headline":"Camaleon CMS - Stored Cross-Site Scripting (XSS) in Comments","id":"CVE-2021-25969","kev_date_added":null,"published":"2021-10-20"},{"cvss_score":6,"headline":"Camaleon CMS AWS Uploader Authenticated Path Traversal Arbitrary File Read","id":"CVE-2026-1776","kev_date_added":null,"published":"2026-03-09"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Stored XSS in Camaleon CMS allows attackers to execute scripts via profile image uploads, though the vendor disputes reproducibility.","url":"https://insights.sbomify.com/CVE-2018-18260/"}