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

Vulnerability in Grav API Plugin (CVE-2026-65896)

Summary

Vulnerability in Grav API Plugin (CVE-2026-65896). Data can be tampered with by attackers. Exploitable via POST /pages/{route}/move.

Original description

The description as published by the source.

Grav API Plugin (Composer package getgrav/grav-plugin-api) before 1.0.10 fails to properly validate the slug field in the POST /pages/{route}/move endpoint. PagesController::move() sanitizes the slug only with ltrim($body['slug'], '.'), which strips leading periods but does not neutralize '/' or '..' segments. An authenticated API caller with the api.pages.write permission can supply path traversal sequences (e.g., 01.home/../../../pwned) to move an entire page directory (content and media) to an arbitrary writable location outside user/pages/, including outside the Grav installation.

Source: GitHub Security Advisories (Global) 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-65896 has been found in Grav API Plugin.
Attackers can target a specific entry point like POST /pages/{route}/move over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Grav API Plugin CVE-2026-65896" on the vendor's site.

CVE-2026-65896 (Grav API Plugin) — CWE-73 / CVSS v3 7.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /pages/{route}/move
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-73) exists in Grav API Plugin. Attackers reach the vulnerable code path via POST /pages/{route}/move.

📍 Affected scope

Check the vendor advisory for the affected versions of Grav API Plugin. Attack surface: POST /pages/{route}/move.

🔥 Severity

Severity: High (CVSS 7.1/10). Data can be tampered with by attackers.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ 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 POST /pages/{route}/move requests with malformed payloads or SQL meta-characters. 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
    Hunt for indicators of compromise detect 
    grep 'POST /pages/{route}/move' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /pages/{route}/move への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Post-deployment verification verify 
    Replay attack against POST /pages/{route}/move on staging to confirm patch closes the vector

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

References

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