Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-62387 high CVSS 7.1

Vulnerability in Grav API plugin (CVE-2026-62387)

Summary

Vulnerability in Grav API plugin (CVE-2026-62387). Confidential information can be exposed externally. Exploitable via Referer header. Mitigation: upgrade to 1.0.0-rc.16 or later.

Original description

The description as published by the source.

The Grav API plugin (getgrav/grav-plugin-api) before 1.0.0-rc.16 shipped Access-Control-Allow-Origin: * as its default CORS configuration on all responses, including authenticated endpoints and preflight (OPTIONS) responses. Because the plugin accepts credentials via the Authorization and X-API-Token headers (set programmatically by JavaScript rather than via cookies), an attacker who obtains a valid access token (e.g., via log leakage, Referer headers, browser history, or network capture) can issue fully authenticated cross-origin requests from any malicious website to read sensitive data and perform write operations as the token's user. Fixed in 1.0.0-rc.16.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-62387 has been found in Grav API plugin.
Attackers can target a specific entry point like Referer header over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.1/10.
What to do: upgrade Grav API plugin to 1.0.0-rc.16 or later.
If unsure, ask your IT team or search "Grav API plugin CVE-2026-62387" on the vendor's site.

CVE-2026-62387 (Grav API plugin) — CWE-942 / CVSS v3 7.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: Referer header
Patched: 1.0.0-rc.16 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-942) exists in Grav API plugin. Attackers reach the vulnerable code path via Referer header without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of Grav API plugin. Attack surface: Referer header.

🔥 Severity

Severity: High (CVSS 7.1/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 1.0.0-rc.16.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Grav API plugin を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade Grav API plugin to 1.0.0-rc.16

    ステージング環境で 1.0.0-rc.16 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details