# CVE-2024-50671: Missing authorization in n/a

> Authenticated users can bypass permission checks to view all user email addresses in the Adapt Authoring Tool.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Nov 2024
- **Updated:** 4 Dec 2024
- **Also known as:** GHSA-ghf3-4f69-3865

## What is CVE-2024-50671?

CVE-2024-50671 is a medium-severity missing authorization vulnerability in n/a, published on 25 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Incorrect access control in Adapt Learning Adapt Authoring Tool <= 0.11.3 allows attackers with Authenticated User roles to obtain email addresses via the "Get users" feature. The vulnerability occurs due to a flaw in permission verification logic, where the wildcard character in permitted URLs grants unintended access to endpoints restricted to users with Super Admin roles. This makes it possible for attackers to disclose the email addresses of all users.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2024-50671?


## How do I fix CVE-2024-50671?

No fix has been published for CVE-2024-50671 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-50671 being exploited?

There is no known exploitation of CVE-2024-50671 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-50671 and fix it if it is affected.

What it is: CVE-2024-50671 is a medium-severity missing authorization vulnerability in n/a, published on 25 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-50671 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/CVE-2024-50671/ (Markdown: https://insights.sbomify.com/CVE-2024-50671/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-50671
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-50671
- OSV: https://osv.dev/vulnerability/CVE-2024-50671

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-50671/
Summaries are generated and may contain mistakes; the official description above is the record.