{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62386 exists.","fix":"No fix has been published for CVE-2026-62386 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-62386 is a high-severity vulnerability in getgrav grav, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-62386 and fix it if it is affected.\n\nWhat it is: CVE-2026-62386 is a high-severity vulnerability in getgrav grav, published on 17 Jul 2026. 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-2026-62386 exists.\n\nAffected product: getgrav grav. 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-62386/ (Markdown: https://insights.sbomify.com/CVE-2026-62386/index.md)","id":"CVE-2026-62386","markdown":"https://insights.sbomify.com/CVE-2026-62386/index.md","name":"CVE-2026-62386","record":{"aliases":["GHSA-cx27-6j8x-h4h6"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Grav CMS API plugin","requires_auth":"none","summary":"Attackers can steal admin JWT tokens from logs or history due to URL exposure, enabling unauthorized API access and privilege escalation.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-598","name":"Use of HTTP Request With Sensitive Query String"}],"description":"The Grav API plugin (getgrav/grav-plugin-api) before 1.0.0-rc.16 accepts JWT access tokens through the ?token= URL query parameter on every API route (JwtAuthenticator::extractBearerToken fallback). Because tokens are embedded in URLs, they are logged verbatim in web server access logs, leaked via the Referer header, stored in browser history, and captured by upstream proxy and CDN logs, exposing valid admin access tokens. A leaked token grants unauthorized API access, including reading configuration and user data, creating admin accounts, modifying system settings, and deleting pages.","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":"Grav \u003c 1.0.0-rc.16 Authentication Bypass via token URL Parameter","id":"CVE-2026-62386","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Grav \u003c 1.0.0-rc.16 CORS Misconfiguration via API Plugin","id":"CVE-2026-62387"},"packages":[],"prev":{"headline":"NLTK 3.9.4 Path Traversal via FrameNet and NKJP Readers","id":"CVE-2026-62385"},"products":["grav"],"published":"2026-07-17","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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-23","vendors":["getgrav"]},"summary":"Attackers can steal admin JWT tokens from logs or history due to URL exposure, enabling unauthorized API access and privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-62386/"}