{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-63407 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-63407 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-63407 is a high-severity vulnerability in getgrav grav-plugin-api, published on 19 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-63407 and fix it if it is affected.\n\nWhat it is: CVE-2026-63407 is a high-severity vulnerability in getgrav grav-plugin-api, published on 19 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-63407 in the wild and no public exploit code.\n\nAffected product: getgrav grav-plugin-api. 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-63407/ (Markdown: https://insights.sbomify.com/CVE-2026-63407/index.md)","id":"CVE-2026-63407","markdown":"https://insights.sbomify.com/CVE-2026-63407/index.md","name":"CVE-2026-63407","record":{"aliases":[],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Grav CMS API plugin","requires_auth":"none","summary":"An attacker can bypass CORS restrictions to read and modify authenticated API data using a stolen token, affecting Grav CMS users.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-942","name":"Permissive Cross-domain Security Policy with Untrusted Domains"}],"description":"Grav API Plugin is a RESTful API for Grav CMS that provides full headless access to your site's content. Prior to 1.0.0-rc.16, the Grav API plugin CorsMiddleware returns Access-Control-Allow-Origin: * and permissive OPTIONS responses for authenticated /api/v1 endpoints. JavaScript from any origin can submit an attacker-obtained JWT through the Authorization or X-API-Token header, read the authenticated response, and perform write operations with the token owner's privileges, enabling data exfiltration and account modification. This issue is fixed in version 1.0.0-rc.16.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Grav API Plugin: CORS 'Access-Control-Allow-Origin: *' on Authenticated API Responses","id":"CVE-2026-63407","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Grav API Plugin: JWT Access Token Accepted via `?token=` URL Query Parameter","id":"CVE-2026-63408"},"packages":[],"prev":{"headline":"AnyCable: Telemetry Subsystem Contains Hardcoded Authentication Token and Transmits CLI Arguments Including Secrets","id":"CVE-2026-63406"},"products":["grav-plugin-api"],"published":"2026-08-19","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-25","vendors":["getgrav"]},"summary":"An attacker can bypass CORS restrictions to read and modify authenticated API data using a stolen token, affecting Grav CMS users.","url":"https://insights.sbomify.com/CVE-2026-63407/"}