{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-54599 exists.","fix":"No fix has been published for CVE-2025-54599 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-54599 is a high-severity authentication bypass vulnerability in n/a, published on 2 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-54599 and fix it if it is affected.\n\nWhat it is: CVE-2025-54599 is a high-severity authentication bypass vulnerability in n/a, published on 2 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-54599 exists.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2025-54599/ (Markdown: https://insights.sbomify.com/CVE-2025-54599/index.md)","id":"CVE-2025-54599","markdown":"https://insights.sbomify.com/CVE-2025-54599/index.md","name":"CVE-2025-54599","record":{"aliases":["GHSA-wgfp-jjc7-g8jv"],"analysis":{"component_type":"web_application","fix_type":"configuration_change","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Bevy Event service","requires_auth":"none","summary":"SSO misconfiguration allows attackers to take over accounts when victims change their email addresses, requiring SSO usage.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"events_and_groups","vendor":"bevy"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"The Bevy Event service through 2025-07-22, as used for eBay Seller Events and other activities, allows account takeover, if SSO is used, when a victim changes the email address that they have configured. To exploit this, an attacker would create their own account and perform an SSO login. The root cause of the issue is SSO misconfiguration.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Auth bypass in n/a","id":"CVE-2025-54599","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Race condition in n/a","id":"CVE-2025-54601"},"packages":[],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2025-54598"},"products":["n/a"],"published":"2025-09-02","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-09-02","vendors":["n/a"]},"summary":"SSO misconfiguration allows attackers to take over accounts when victims change their email addresses, requiring SSO usage.","url":"https://insights.sbomify.com/CVE-2025-54599/"}