Site-wide security control changes via omitted scope
Published Jul 23, 2026 · Updated Jul 23, 2026
Missing authorization in Grav API Plugin before 1.0.10 allows remote authenticated users to alter site-wide API security settings. ConfigController::assertScopeAllowed() omits plugins/api from both privileged-scope lists, so PATCH /config/plugins/api accepts rate-limit and CORS changes from api.config.write credentials. The caller needs an authenticated API credential with api.config.write but not api.super; disabling throttling enables credential guessing, while widened CORS is not a demonstrated session-theft path.
Summary
What happened
Missing authorization in Grav API Plugin before 1.0.10 allows remote authenticated users to alter site-wide API security settings. ConfigController::assertScopeAllowed() omits plugins/api from both privileged-scope lists, so PATCH /config/plugins/api accepts rate-limit and CORS changes from api.config.write credentials. The caller needs an authenticated API credential with api.config.write but not api.super; disabling throttling enables credential guessing, while widened CORS is not a demonstrated session-theft path.
The record
- CVE
- CVE-2026-65895
- Published
- Jul 23, 2026
- Updated
- Jul 23, 2026
- Vendor
- Grav
- Product
- Grav API Plugin
- Classifications
- CWE-862, T1562.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 23, 2026CVE publishedPublication date reported by the CVE source.
- Jul 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.0.10
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Authenticated API configuration-write proof of conceptfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo