{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-63313 exists.","fix":"No fix has been published for CVE-2026-63313 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-63313 is a high-severity server-side request forgery vulnerability in decolua 9router, published on 23 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-63313 and fix it if it is affected.\n\nWhat it is: CVE-2026-63313 is a high-severity server-side request forgery vulnerability in decolua 9router, published on 23 Jul 2026. 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-2026-63313 exists.\n\nAffected product: decolua 9router. 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-2026-63313/ (Markdown: https://insights.sbomify.com/CVE-2026-63313/index.md)","id":"CVE-2026-63313","markdown":"https://insights.sbomify.com/CVE-2026-63313/index.md","name":"CVE-2026-63313","record":{"aliases":["GHSA-5853-q5hg-7gx5"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"9Router server","requires_auth":"low_privilege","summary":"An authenticated user can exploit SSRF in 9Router to access internal services and cloud metadata credentials via the /v1/web/fetch endpoint.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"9Router before 0.4.72 contains a server-side request forgery (SSRF) vulnerability in the /v1/web/fetch endpoint. The endpoint accepts a user-controlled url parameter and passes it to a configured external scraping provider (Firecrawl, Jina Reader, Tavily, or Exa) to fetch content. The URL is only validated as syntactically valid via new URL() with no blocklist for private IP ranges, cloud metadata endpoints (e.g., 169.254.169.254), link-local addresses, or internal hostnames. An authenticated or locally-connected user can cause the server to fetch arbitrary internal URLs and have the response content returned, enabling read-access SSRF that can expose cloud metadata credentials, reach internal services, and bypass authentication on localhost endpoints.","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":"9Router before 0.4.72 Server-Side Request Forgery via /v1/web/fetch","id":"CVE-2026-63313","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"SQL Injection in WebCTI","id":"CVE-2026-63314"},"packages":[],"prev":{"headline":"NLTK StreamBackedCorpusView Bypasses pathsec.ENFORCE Arbitrary File Read","id":"CVE-2026-63312"},"products":["9router"],"published":"2026-07-23","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"2026-07-24","vendors":["decolua"]},"summary":"An authenticated user can exploit SSRF in 9Router to access internal services and cloud metadata credentials via the /v1/web/fetch endpoint.","url":"https://insights.sbomify.com/CVE-2026-63313/"}