# CVE-2024-38183: GroupMe Elevation of Privilege Vulnerability

> An unauthenticated attacker can elevate privileges in GroupMe due to improper access control, requiring a patch from Microsoft.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Sep 2024
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-hqpj-xx46-mwvh

## What is CVE-2024-38183?

CVE-2024-38183 is a critical authentication bypass vulnerability in Microsoft GroupMe, published on 17 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An improper access control vulnerability in GroupMe allows an a unauthenticated attacker to elevate privileges over a network.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Microsoft Groupme.

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

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

## Is CVE-2024-38183 being exploited?

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

## Other vulnerabilities in Microsoft GroupMe

- [CVE-2024-38164](https://insights.sbomify.com/CVE-2024-38164/): GroupMe Elevation of Privilege Vulnerability (critical 9.6)
- [CVE-2024-38176](https://insights.sbomify.com/CVE-2024-38176/): GroupMe Elevation of Privilege Vulnerability (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-38183 is a critical authentication bypass vulnerability in Microsoft GroupMe, published on 17 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-38183 in the wild and no public exploit code.

Affected product: Microsoft GroupMe. 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-38183/ (Markdown: https://insights.sbomify.com/CVE-2024-38183/index.md)
```

## Sources

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

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