{"answers":{"affected":"2 open source packages ship an affected version, including silverstripe/cms.","exploited":"There is no known exploitation of GHSA-6hh6-59j2-qrxw in the wild and no public exploit code.","fix":"Upgrade silverstripe/cms to 3.1.10 or later.","what":"GHSA-6hh6-59j2-qrxw is a cross-site scripting vulnerability in silverstripe/cms, published on 22 May 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for GHSA-6hh6-59j2-qrxw and fix it if it is affected.\n\nWhat it is: GHSA-6hh6-59j2-qrxw is a cross-site scripting vulnerability in silverstripe/cms, published on 22 May 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of GHSA-6hh6-59j2-qrxw in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- silverstripe/cms (Packagist): affected from 3.1.0; fixed in 3.1.10\n- silverstripe/cms (Packagist): affected from 3.1.0; fixed in 3.1.10\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/GHSA-6hh6-59j2-qrxw/ (Markdown: https://insights.sbomify.com/GHSA-6hh6-59j2-qrxw/index.md)","id":"GHSA-6hh6-59j2-qrxw","markdown":"https://insights.sbomify.com/GHSA-6hh6-59j2-qrxw/index.md","name":"GHSA-6hh6-59j2-qrxw","record":{"aliases":[],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Silverstripe CMS plugin","requires_auth":"low_privilege","summary":"An attacker with CMS access can inject malicious HTML into page history, leading to XSS when compare mode is used.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"A cross-site scripting vulnerability has been discovered in the CMS page history tab.\n\nThis vulnerability can only be exploited if a user with CMS access has posted malicious or unescaped HTML into any of the text fields on a page, and if the \"compare mode\" option is selected. The HTML will be embedded into the page unescaped.\n\nThis has been resolved by performing the text comparison in a HTML friendly way.","ecosystems":["Packagist"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Silverstripe History XSS Vulnerability","id":"GHSA-6hh6-59j2-qrxw","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"xss","year":"2024"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["3.1.10"],"introduced":["3.1.0"],"last_affected":[],"package":"silverstripe/cms","purl":null,"source":"GHSA-6hh6-59j2-qrxw"},{"ecosystem":"Packagist","fixed":["3.1.10"],"introduced":["3.1.0"],"last_affected":[],"package":"silverstripe/cms","purl":"pkg:composer/silverstripe/cms","source":"GHSA-6hh6-59j2-qrxw"}],"products":null,"published":"2024-05-22","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"An attacker with CMS access can inject malicious HTML into page history, leading to XSS when compare mode is used.","url":"https://insights.sbomify.com/GHSA-6hh6-59j2-qrxw/"}