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.
Casky was already ahead
This CVE exploits attack patterns that Casky's 0matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.
CVE-2026-75830 is a path traversal vulnerability affecting Grav's plugin API versions 1.0.0-beta.10 through 1.0.14. The vulnerability exists in the PagesController::batchCopy() method where the 'suffix' parameter accepts user input via POST requests to /api/v1/pages/batch without proper validation. An authenticated user with editor-level permissions (api.pages.write) can inject path traversal sequences like /../../../ to escape the intended user/pages/ directory and potentially read, write, or manipulate files outside the intended scope. This is particularly concerning because it requires only mid-level API permissions rather than super-admin access, significantly expanding the attack surface for compromised editor accounts or malicious insiders.
While MITRE ATT&CK techniques aren't formally mapped to this CVE, Casky.ai's Claude-powered analysis would identify this as a file system access vulnerability related to Defense Evasion (T1548) and lateral movement techniques. Practitioners using Casky would see findings highlighting the unvalidated user input in API parameters, the insufficient path normalization that allows directory traversal, and the permission model weakness that grants dangerous file operations to non-administrative accounts. The platform's extended reasoning would flag this as a regression—an incomplete fix to a previous vulnerability (GHSA-qjq4-jp55-4mx2)—helping security teams recognize patterns of remediation failures that often indicate areas requiring deeper code review and validation testing.
Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →
Casky has 0 skills that investigate the attack patterns behind CVE-2026-75830. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation