# GHSA-36mj-6r7r-mqhf: User can obtain JWT token even if account is disabled

> Disabled users can obtain JWT tokens to bypass access controls, requiring an upgrade to the eZ Platform REST library.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Sep 2021

## What is GHSA-36mj-6r7r-mqhf?

GHSA-36mj-6r7r-mqhf is an authentication bypass vulnerability in ezsystems/ezplatform-rest, published on 29 Sep 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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

## Which versions are affected by GHSA-36mj-6r7r-mqhf?

2 open source packages ship an affected version, including ezsystems/ezplatform-rest.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ezsystems/ezplatform-rest` | Packagist | From 1.3.0 | 1.3.8 |
| `ezsystems/ezplatform-rest` | Packagist | From 1.3.0 | 1.3.8 |

## How do I fix GHSA-36mj-6r7r-mqhf?

Upgrade ezsystems/ezplatform-rest to 1.3.8 or later.

## Is GHSA-36mj-6r7r-mqhf being exploited?

There is no known exploitation of GHSA-36mj-6r7r-mqhf in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-36mj-6r7r-mqhf and fix it if it is affected.

What it is: GHSA-36mj-6r7r-mqhf is an authentication bypass vulnerability in ezsystems/ezplatform-rest, published on 29 Sep 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-36mj-6r7r-mqhf in the wild and no public exploit code.

Affected packages and fixed versions:
- ezsystems/ezplatform-rest (Packagist): affected from 1.3.0; fixed in 1.3.8
- ezsystems/ezplatform-rest (Packagist): affected from 1.3.0; fixed in 1.3.8

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-36mj-6r7r-mqhf/ (Markdown: https://insights.sbomify.com/GHSA-36mj-6r7r-mqhf/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-36mj-6r7r-mqhf

---
From sbomify Insights: https://insights.sbomify.com/GHSA-36mj-6r7r-mqhf/
Summaries are generated and may contain mistakes; the official description above is the record.