{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-28096 exists.","fix":"No fix has been published for CVE-2025-28096 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-28096 is a medium-severity server-side request forgery vulnerability in n/a, published on 28 Mar 2025. 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 CVE-2025-28096 and fix it if it is affected.\n\nWhat it is: CVE-2025-28096 is a medium-severity server-side request forgery vulnerability in n/a, published on 28 Mar 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-28096 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-28096/ (Markdown: https://insights.sbomify.com/CVE-2025-28096/index.md)","id":"CVE-2025-28096","markdown":"https://insights.sbomify.com/CVE-2025-28096/index.md","name":"CVE-2025-28096","record":{"aliases":["GHSA-9qpf-q9v6-4q5c"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"OneNav bookmark manager","requires_auth":"low_privilege","summary":"An attacker can exploit SSRF in OneNav custom headers to access internal resources or bypass security controls.","user_interaction":"required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"onenav","vendor":"onenav"}],"cvss":{"score":5.4,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"OneNav 1.1.0 is vulnerable to Server-Side Request Forgery (SSRF) in custom headers.","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":"Server-side request forgery in n/a","id":"CVE-2025-28096","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-28097"},"packages":[],"prev":{"headline":"ShopXO Vulnerable to Server-Side Request Forgery (SSRF) and Cross-Site Scripting (XSS)","id":"CVE-2025-28094"},"products":["n/a"],"published":"2025-03-28","related":[{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2021-38712","kev_date_added":null,"published":"2021-08-16"},{"cvss_score":7.3,"headline":"OneNav API improper authentication","id":"CVE-2023-7210","kev_date_added":null,"published":"2024-01-07"},{"cvss_score":5.5,"headline":"Cross-site scripting in n/a","id":"CVE-2025-28097","kev_date_added":null,"published":"2025-03-28"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2021-38138","kev_date_added":null,"published":"2021-08-05"},{"cvss_score":5.3,"headline":"Path traversal in n/a","id":"CVE-2022-26276","kev_date_added":null,"published":"2022-03-12"}],"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-03-31","vendors":["n/a"]},"summary":"An attacker can exploit SSRF in OneNav custom headers to access internal resources or bypass security controls.","url":"https://insights.sbomify.com/CVE-2025-28096/"}