{"answers":{"affected":"2 open source packages ship an affected version, including silverstripe/framework.","exploited":"There is no known exploitation of GHSA-qp29-wcc2-vmpc in the wild and no public exploit code.","fix":"Upgrade silverstripe/framework to 3.2.1 or later.","what":"GHSA-qp29-wcc2-vmpc is a server-side request forgery vulnerability in silverstripe/framework, published on 23 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-qp29-wcc2-vmpc and fix it if it is affected.\n\nWhat it is: GHSA-qp29-wcc2-vmpc is a server-side request forgery vulnerability in silverstripe/framework, published on 23 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-qp29-wcc2-vmpc in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- silverstripe/framework (Packagist): affected from 3.0.0; fixed in 3.2.1\n- silverstripe/framework (Packagist): affected from 3.0.0; fixed in 3.2.1\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-qp29-wcc2-vmpc/ (Markdown: https://insights.sbomify.com/GHSA-qp29-wcc2-vmpc/index.md)","id":"GHSA-qp29-wcc2-vmpc","markdown":"https://insights.sbomify.com/GHSA-qp29-wcc2-vmpc/index.md","name":"GHSA-qp29-wcc2-vmpc","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Silverstripe CMS","requires_auth":"low_privilege","summary":"Insufficient server-side URL sanitization in Silverstripe CMS allows potential Server-Side Request Forgery via the HTML editor's media embedding feature.","user_interaction":"required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"\"Add from URL\" doesn't clearly sanitise URL server side\n\nHtmlEditorField_Toolbar has an action HtmlEditorField_Toolbar#viewfile, which gets called by the CMS when adding a media \"from a URL\" (i.e. via oembed).\n\nThis action gets the URL to add in the GET parameter FileURL. However it doesn't do any URL sanitising server side. The current logic will pass this through to Oembed, which will probably reject most dangerous URLs, but it's possible future changes would break this.","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 HtmlEditor embed url sanitisation","id":"GHSA-qp29-wcc2-vmpc","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"ssrf","year":"2024"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["3.2.1"],"introduced":["3.0.0"],"last_affected":[],"package":"silverstripe/framework","purl":null,"source":"GHSA-qp29-wcc2-vmpc"},{"ecosystem":"Packagist","fixed":["3.2.1"],"introduced":["3.0.0"],"last_affected":[],"package":"silverstripe/framework","purl":"pkg:composer/silverstripe/framework","source":"GHSA-qp29-wcc2-vmpc"}],"products":null,"published":"2024-05-23","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":"Insufficient server-side URL sanitization in Silverstripe CMS allows potential Server-Side Request Forgery via the HTML editor's media embedding feature.","url":"https://insights.sbomify.com/GHSA-qp29-wcc2-vmpc/"}