{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65096 exists.","fix":"No fix has been published for CVE-2025-65096 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-65096 is a medium-severity missing authorization vulnerability in rommapp romm, published on 3 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-65096 and fix it if it is affected.\n\nWhat it is: CVE-2025-65096 is a medium-severity missing authorization vulnerability in rommapp romm, published on 3 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65096 exists.\n\nAffected product: rommapp romm. 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-65096/ (Markdown: https://insights.sbomify.com/CVE-2025-65096/index.md)","id":"CVE-2025-65096","markdown":"https://insights.sbomify.com/CVE-2025-65096/index.md","name":"CVE-2025-65096","record":{"aliases":["GHSA-5ghc-8wr3-788c"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"ROM Manager","requires_auth":"low_privilege","summary":"Attackers can access private collections belonging to other users by directly accessing their IDs via the API without proper ownership verification.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"romm","vendor":"romm.app"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"},{"id":"CWE-284","name":"Improper Access Control"}],"description":"RomM (ROM Manager) allows users to scan, enrich, browse and play their game collections with a clean and responsive interface. Prior to 4.4.1 and 4.4.1-beta.2, users can read private collections / smart collections belonging to other users by directly accessing their IDs via API. No ownership verification or checking if the collection is public/private before returning collection data. This vulnerability is fixed in 4.4.1 and 4.4.1-beta.2.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"RomM Insecure Direct Object Reference (IDOR) Allows Unauthorized Access to Private Collections","id":"CVE-2025-65096","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Insecure Direct Object Reference (IDOR) Allows Unauthorized Deletion of User Collections","id":"CVE-2025-65097"},"packages":[],"prev":{"headline":"Lookyloo is vulnerable due to improper user input sanitization","id":"CVE-2025-65095"},"products":["romm"],"published":"2025-12-03","related":[{"cvss_score":7.6,"headline":"RomM Chained XSS and CSRF Vulnerabilities Enable Admin Account Takeover","id":"CVE-2025-65027","kev_date_added":null,"published":"2025-12-03"},{"cvss_score":7.1,"headline":"Insecure Direct Object Reference (IDOR) Allows Unauthorized Deletion of User Collections","id":"CVE-2025-65097","kev_date_added":null,"published":"2025-12-03"}],"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-12-03","vendors":["rommapp"]},"summary":"Attackers can access private collections belonging to other users by directly accessing their IDs via the API without proper ownership verification.","url":"https://insights.sbomify.com/CVE-2025-65096/"}