PatchSiren cyber security CVE debrief
CVE-2026-65895 getgrav CVE debrief
The CVE-2026-65895 vulnerability affects Grav API Plugin versions before 1.0.10, allowing authenticated users with 'api.config.write' privileges to modify security-critical plugin configuration scopes. This could lead to credential brute-forcing attacks and CORS policy changes. The vulnerability has a CVSS score of 8.2 and is classified as HIGH. Administrators and users should be aware of this vulnerability and take immediate action to update or mitigate it. The CVE record was published on 2026-07-23T12:18:47.910Z and has not been modified since then. To address this vulnerability, review and restrict 'api.config.write' privileges, implement additional monitoring, update Grav API Plugin to version 1.0.10 or later, conduct regular inventory checks, and consider compensating controls for credential brute-forcing attacks.
- Vendor
- getgrav
- Product
- grav
- CVSS
- HIGH 8.2
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-07-23
- Original CVE updated
- 2026-08-28
- Advisory published
- 2026-07-23
- Advisory updated
- 2026-08-28
Who should care
Administrators and users of Grav API Plugin, especially those with 'api.config.write' privileges, should be aware of this vulnerability and take immediate action to update or mitigate it.
Technical summary
The Grav API Plugin versions before 1.0.10 fail to restrict write access to security-critical plugin configuration scopes. This allows authenticated users with 'api.config.write' privilege to modify rate limiting and CORS settings. Attackers can exploit this to disable rate limiting site-wide, enabling credential brute-forcing attacks, and reconfigure CORS policies to include attacker-controlled origins with credentials enabled. The vulnerability has a CVSS score of 8.2 and is classified as HIGH.
Defensive priority
Authenticated users with limited privileges can modify critical settings, allowing potential credential brute-forcing attacks and CORS policy changes.
Recommended defensive actions
- Review and restrict 'api.config.write' privileges to only necessary users
- Implement additional monitoring for changes to rate limiting and CORS settings
- Update Grav API Plugin to version 1.0.10 or later
- Conduct regular inventory checks for plugin versions and user privileges
- Consider compensating controls for credential brute-forcing attacks
Evidence notes
The CVE-2026-65895 record indicates that Grav API Plugin versions before 1.0.10 are vulnerable due to insufficient access restrictions on security-critical plugin configuration scopes. Authenticated users with the 'api.config.write' privilege can modify rate limiting and CORS settings. This could allow attackers to disable rate limiting site-wide, enabling credential brute-forcing attacks, and reconfigure CORS policies to include attacker-controlled origins with credentials enabled. The CVSS score is 8.2, classified as HIGH.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-65895 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-65895
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-65895 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-65895
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/getgrav/grav-plugin-api/commit/f9438d4e71389b1041ac60b69b0b5714ecfa3bdd
-
Source reference
Unverified legacy reference
URL: https://github.com/getgrav/grav/security/advisories/GHSA-4pqv-2qj5-38fp
-
Source reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/grav-api-plugin-before-broken-access-control
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.