Inadequate access control vulnerability in Fullstep
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fullstep | Fullstep | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fullstep | Fullstep |
|
Vendor Solution
The vulnerability has been fixed by the Fullstep team in version 5.30.07, which has been available in production since January 29, 2026.
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.270% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Inadequate access control in the registration process in Fullstep V5, which could allow unauthenticated users to obtain a valid JWT token with which to interact with authenticated API resources. Successful exploitation of this vulnerability could allow an unauthenticated attacker to compromise the confidentiality of the affected resource, provided they have a valid token with which to interact with the API. | |
| Title | Inadequate access control vulnerability in Fullstep | |
| First Time appeared |
Fullstep
Fullstep fullstep |
|
| Weaknesses | CWE-306 | |
| CPEs | cpe:2.3:a:fullstep:fullstep:5.30.07:*:*:*:*:*:*:* cpe:2.3:a:fullstep:fullstep:5:*:*:*:*:*:*:* |
|
| Vendors & Products |
Fullstep
Fullstep fullstep |
|
| References |
| |
| Metrics |
cvssV4_0
|