User can obtain JWT token even if account is disabled
Priority LOW 38CWE-284Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-284.
Summary
Users can authenticate this way even if their user account is disabled. This is a high risk vulnerability when account disabling is used to block users' access to the system. (Someone who never had an account cannot exploit this vulnerability.) The fix ensures tokens are generated only for enabled user accounts, and is distributed via Composer as ezsystems/ezplatform-rest v1.3.8
Why it matters now
Fix Fixed ezsystems/ezplatform-rest (Packagist): 1.3.8
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | ezsystems/ezplatform-rest (Packagist) | 1.3.0 to before 1.3.8 | 1.3.8 | Patch available | GHSA-36mj-6r7r-mqhf |
- ezsystems/ezplatform-rest (Packagist) Vendor— Affected 1.3.0 to before 1.3.8 Fixed in 1.3.8 Patch available GHSA-36mj-6r7r-mqhf
Remediation
- Fix · GHSA-36mj-6r7r-mqhf ezsystems/ezplatform-rest (Packagist) Fixed in 1.3.8 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-36mj-6r7r-mqhf
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences