Quick answers
- Is CVE-2026-65895 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-65895 being exploited in the wild.
- How severe is CVE-2026-65895?
- High severity, with a CVSS score of 8.5, published 23 July 2026.
- Which products and versions are affected?
- Grav API Plugin < 1.0.10.
- Is there a fix for CVE-2026-65895?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-65895 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-65895?
- Check whether you run Grav API Plugin at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A broken access control vulnerability exists in the ConfigController of the Grav API Plugin. The component fails to include the 'plugins/api' scope within its 'SUPER_WRITE_SCOPES' or 'PRIVILEGED_SCOPES' constants, which are intended to gate security-sensitive configurations. Consequently, an authenticated user possessing only the 'api.config.write' permission (rather than 'api.super') can issue PATCH requests to /config/plugins/api. This allows an attacker to disable site-wide rate limiting, facilitating brute-force attacks, or modify CORS policies to include attacker-controlled origins with credentials enabled. The issue is resolved in version 1.0.10.
Affected products
- getgrav Grav API Plugin < 1.0.10
Timeline
- 2026-07-09: advisory: GitHub Security Advisory published
- 2026-07-23: disclosed: NVD publication date