{"answers":{"affected":"2 open source packages ship an affected version, including silverstripe/framework.","exploited":"There is no known exploitation of GHSA-256q-hx8w-xcqx in the wild and no public exploit code.","fix":"Upgrade silverstripe/framework to 5.3.23 or later.","what":"GHSA-256q-hx8w-xcqx is a vulnerability in silverstripe/framework, published on 10 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-256q-hx8w-xcqx and fix it if it is affected.\n\nWhat it is: GHSA-256q-hx8w-xcqx is a vulnerability in silverstripe/framework, published on 10 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-256q-hx8w-xcqx in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- silverstripe/framework (Packagist): affected from 4.0.0; fixed in 5.3.23\n- silverstripe/framework (Packagist): affected from 4.0.0; fixed in 5.3.23\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-256q-hx8w-xcqx/ (Markdown: https://insights.sbomify.com/GHSA-256q-hx8w-xcqx/index.md)","id":"GHSA-256q-hx8w-xcqx","markdown":"https://insights.sbomify.com/GHSA-256q-hx8w-xcqx/index.md","name":"GHSA-256q-hx8w-xcqx","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Silverstripe CMS","requires_auth":"none","summary":"Attackers can enumerate valid usernames by measuring response times on login and password reset forms in Silverstripe CMS.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Impact\nUser enumeration is possible by performing a timing attack on the login or password reset pages with user credentials.\n\nThis was originally disclosed in https://www.silverstripe.org/download/security-releases/ss-2017-005/ for CMS 3 but was not patched in CMS 4+\n\n### References\n\n- https://www.silverstripe.org/download/security-releases/ss-2017-005\n- https://www.silverstripe.org/download/security-releases/ss-2025-001","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 Framework user enumeration via timing attack on login and password reset forms","id":"GHSA-256q-hx8w-xcqx","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["5.3.23"],"introduced":["4.0.0"],"last_affected":[],"package":"silverstripe/framework","purl":null,"source":"GHSA-256q-hx8w-xcqx"},{"ecosystem":"Packagist","fixed":["5.3.23"],"introduced":["4.0.0"],"last_affected":[],"package":"silverstripe/framework","purl":"pkg:composer/silverstripe/framework","source":"GHSA-256q-hx8w-xcqx"}],"products":null,"published":"2025-04-10","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":"Attackers can enumerate valid usernames by measuring response times on login and password reset forms in Silverstripe CMS.","url":"https://insights.sbomify.com/GHSA-256q-hx8w-xcqx/"}