{"answers":{"affected":"2 open source packages ship an affected version, including ibexa/user.","exploited":"There is no known exploitation of GHSA-q3x8-6898-23g3 in the wild and no public exploit code.","fix":"Upgrade ibexa/user to 5.0.3 or later.","what":"GHSA-q3x8-6898-23g3 is a vulnerability in ibexa/user, published on 17 Oct 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-q3x8-6898-23g3 and fix it if it is affected.\n\nWhat it is: GHSA-q3x8-6898-23g3 is a vulnerability in ibexa/user, published on 17 Oct 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-q3x8-6898-23g3 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ibexa/user (Packagist): affected from 5.0.0; fixed in 5.0.3\n- ibexa/user (Packagist): affected from 5.0.0; fixed in 5.0.3\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-q3x8-6898-23g3/ (Markdown: https://insights.sbomify.com/GHSA-q3x8-6898-23g3/index.md)","id":"GHSA-q3x8-6898-23g3","markdown":"https://insights.sbomify.com/GHSA-q3x8-6898-23g3/index.md","name":"GHSA-q3x8-6898-23g3","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Ibexa CMS","requires_auth":"none","summary":"Attackers can enumerate valid user accounts via ambiguous login error messages in the Ibexa back-office.","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\nIn v5, error messages could provide enough information to tell whether a user exists or not. This is resolved by ensuring the error messages are sufficiently ambigious.\n\n### Patches\nSee \"Patched versions\".\n\n### Workarounds\nNone.\n\n### Resources\nhttps://developers.ibexa.co/security-advisories/ibexa-sa-2025-004-xss-and-enumeration-vulnerabilities-in-back-office","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":"ibexa/user login enumerates user accounts","id":"GHSA-q3x8-6898-23g3","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.0.3"],"introduced":["5.0.0"],"last_affected":[],"package":"ibexa/user","purl":null,"source":"GHSA-q3x8-6898-23g3"},{"ecosystem":"Packagist","fixed":["5.0.3"],"introduced":["5.0.0"],"last_affected":[],"package":"ibexa/user","purl":"pkg:composer/ibexa/user","source":"GHSA-q3x8-6898-23g3"}],"products":null,"published":"2025-10-17","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 user accounts via ambiguous login error messages in the Ibexa back-office.","url":"https://insights.sbomify.com/GHSA-q3x8-6898-23g3/"}