Vulnerability in grav-plugin-api (CVE-2026-75830)
Summary
Vulnerability in grav-plugin-api (CVE-2026-75830). Data can be tampered with by attackers. Exploitable via POST /api/v1/pages/batch. Mitigation: upgrade to 1.0.15 or later.
Original description
The description as published by the source.
grav-plugin-api (getgrav/grav-plugin-api) versions >= 1.0.0-beta.10 and <= 1.0.14 contain a path traversal vulnerability in the PagesController::batchCopy() method. An incomplete fix for GHSA-qjq4-jp55-4mx2 left the user-controlled 'suffix' parameter (via POST /api/v1/pages/batch) unvalidated. An authenticated user with the api.pages.write permission (editor-level, not super-admin) can supply path traversal sequences (e.g. /../../../) in the suffix parameter to escape the intended user/pages/ directory and write attacker-controlled page content and page media to arbitrary filesystem locations writable by the web server process. The vulnerability is fixed in 1.0.15.
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-75830 has been found in grav-plugin-api.
Attackers can target a specific entry point like POST /api/v1/pages/batch over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.1/10.
What to do: upgrade grav-plugin-api to 1.0.15 or later.
If unsure, ask your IT team or search "grav-plugin-api CVE-2026-75830" on the vendor's site.
CVE-2026-75830 (grav-plugin-api) — CWE-73 / CVSS v3 7.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/v1/pages/batch
Patched: 1.0.15 — 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.
A vulnerability (CWE-73) exists in grav-plugin-api. Attackers reach the vulnerable code path via POST /api/v1/pages/batch.
Check the vendor advisory for the affected versions of grav-plugin-api. Attack surface: POST /api/v1/pages/batch.
Severity: High (CVSS 7.1/10). Data can be tampered with by attackers.
Update to 1.0.15.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /api/v1/pages/batch requests with malformed payloads or SQL meta-characters. Run grep -r 'grav-plugin-api' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'grav-plugin-api' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
grav-plugin-apiを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /api/v1/pages/batch' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/v1/pages/batchへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade grav-plugin-api to 1.0.15ステージング環境で 1.0.15 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /api/v1/pages/batch on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- web github.com
- web nvd.nist.gov
- web disclosure@vulncheck.com
- web github.com