getgrav grav-plugin-api up to 1.0.0-beta.14 UsersController::update authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in getgrav grav-plugin-api up to 1.0.0-beta.14. Affected by this vulnerability is the function UsersController::update. This manipulation causes authorization.
This vulnerability is registered as CVE-2026-42843. Remote exploitation of the attack is possible. No exploit is available.
It is recommended to upgrade the affected component.
Details
A vulnerability was found in getgrav grav-plugin-api up to 1.0.0-beta.14. It has been declared as critical. Affected by this vulnerability is the function UsersController::update. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-863. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Grav API Plugin is a RESTful API for Grav CMS that provides full headless access to your site's content, media, configuration, users, and system management. Prior to 1.0.0-beta.15, an insecure direct object reference and logic flaw in the Grav API plugin (UsersController::update) allows any authenticated user with basic API access (api.access) to modify their own permission configuration. An attacker can exploit this to escalate their privileges to Super Administrator (admin.super and api.super), leading to full system compromise and potential RCE. This vulnerability is fixed in 1.0.0-beta.15.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-42843 since 04/30/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details are known, but no exploit is available.
Upgrading to version 1.0.0-beta.15 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
- 1.0.0-beta.0
- 1.0.0-beta.1
- 1.0.0-beta.2
- 1.0.0-beta.3
- 1.0.0-beta.4
- 1.0.0-beta.5
- 1.0.0-beta.6
- 1.0.0-beta.7
- 1.0.0-beta.8
- 1.0.0-beta.9
- 1.0.0-beta.10
- 1.0.0-beta.11
- 1.0.0-beta.12
- 1.0.0-beta.13
- 1.0.0-beta.14
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.4
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.8
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-863 / CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: grav-plugin-api 1.0.0-beta.15
Timeline
04/30/2026 CVE reserved05/11/2026 Advisory disclosed
05/11/2026 VulDB entry created
05/11/2026 VulDB entry last update
Sources
Advisory: GHSA-r945-h4vm-h736Status: Confirmed
CVE: CVE-2026-42843 (🔒)
GCVE (CVE): GCVE-0-2026-42843
GCVE (VulDB): GCVE-100-362725
Entry
Created: 05/11/2026 20:36Changes: 05/11/2026 20:36 (65)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.