{"answers":{"affected":"2 open source packages ship an affected version, including silverstripe/framework. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-32981 in the wild and no public exploit code.","fix":"Upgrade silverstripe/framework to 5.2.16 or later.","what":"CVE-2024-32981 is a medium-severity cross-site scripting vulnerability in silverstripe-framework, published on 17 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-32981 and fix it if it is affected.\n\nWhat it is: CVE-2024-32981 is a medium-severity cross-site scripting vulnerability in silverstripe-framework, published on 17 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-32981 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- silverstripe/framework (Packagist): affected all versions; fixed in 5.2.16\n- silverstripe/framework (Packagist): affected all versions; fixed in 5.2.16\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-2024-32981/ (Markdown: https://insights.sbomify.com/CVE-2024-32981/index.md)","id":"CVE-2024-32981","markdown":"https://insights.sbomify.com/CVE-2024-32981/index.md","name":"CVE-2024-32981","record":{"aliases":["GHSA-chx7-9x8h-r5mg"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Silverstripe CMS framework","requires_auth":"low_privilege","summary":"An attacker with CMS edit access can inject JavaScript via encoded payloads bypassing server-side sanitization, requiring an upgrade to Silverstripe framework.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"framework","vendor":"silverstripe"}],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Silverstripe framework is the PHP framework forming the base for the Silverstripe CMS. In affected versions a bad actor with access to edit content in the CMS could add send a specifically crafted encoded payload to the server, which could be used to inject a JavaScript payload on the front end of the site. The payload would be sanitised on the client-side, but server-side sanitisation doesn't catch it. The server-side sanitisation logic has been updated to sanitise against this type of attack in version 5.2.16. All users are advised to upgrade. There are no known workarounds for this vulnerability.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Cross-site Scripting vulnerability with encoded payload in silverstripe/framework","id":"CVE-2024-32981","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"xss","year":"2024"},"n_packages":2,"n_references":3,"next":{"headline":"Litestar and Starlite affected by Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')","id":"CVE-2024-32982"},"packages":[{"ecosystem":"Packagist","fixed":["5.2.16"],"introduced":["0"],"last_affected":[],"package":"silverstripe/framework","purl":null,"source":"GHSA-chx7-9x8h-r5mg"},{"ecosystem":"Packagist","fixed":["5.2.16"],"introduced":["0"],"last_affected":[],"package":"silverstripe/framework","purl":"pkg:composer/silverstripe/framework","source":"GHSA-chx7-9x8h-r5mg"}],"prev":{"headline":"Spin contains a potential network sandbox escape for specifically configured Spin applications","id":"CVE-2024-32980"},"products":["silverstripe-framework"],"published":"2024-07-17","related":[{"cvss_score":8.8,"headline":"Blind SQL Injection via GridFieldSortableHeader","id":"CVE-2022-38148","kev_date_added":null,"published":"2022-11-21"},{"cvss_score":6.1,"headline":"Reflected XSS in querystring parameters","id":"CVE-2022-38462","kev_date_added":null,"published":"2022-11-22"},{"cvss_score":5.4,"headline":"Silverstripe Framework has a XSS vulnerability in HTML editor","id":"CVE-2025-30148","kev_date_added":null,"published":"2025-04-10"},{"cvss_score":5.4,"headline":"Cross-site Scripting in form messages in silverstripe framework","id":"CVE-2024-53277","kev_date_added":null,"published":"2025-01-14"},{"cvss_score":5.4,"headline":"Silverstripe Framework has open redirect vulnerability on CMSSecurity relogin screen","id":"CVE-2023-22729","kev_date_added":null,"published":"2023-04-26"},{"cvss_score":5.4,"headline":"Stored XSS using HTMLEditor","id":"CVE-2022-37429","kev_date_added":null,"published":"2022-11-23"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["silverstripe"]},"summary":"An attacker with CMS edit access can inject JavaScript via encoded payloads bypassing server-side sanitization, requiring an upgrade to Silverstripe framework.","url":"https://insights.sbomify.com/CVE-2024-32981/"}