# CVE-2023-44794: SaToken privilege escalation vulnerability

> A remote attacker can escalate privileges by sending a crafted payload to the URL in the Dromara SaToken library.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Oct 2023
- **Updated:** 12 Sep 2024
- **Also known as:** GHSA-54f6-9mx9-86f7

## What is CVE-2023-44794?

CVE-2023-44794 is a critical vulnerability in n/a, published on 25 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in Dromara SaToken version 1.36.0 and before allows a remote attacker to escalate privileges via a crafted payload to the URL.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2023-44794?

2 open source packages ship an affected version, including cn.dev33:sa-token-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cn.dev33:sa-token-core` | Maven | All versions | 1.37.0 |
| `cn.dev33:sa-token-core` | Maven | All versions | 1.37.0 |

Products: Dromara Sa-Token.

## How do I fix CVE-2023-44794?

Upgrade cn.dev33:sa-token-core to 1.37.0 or later.

## Is CVE-2023-44794 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-44794 exists.

## Other vulnerabilities in n/a

- [CVE-2023-43961](https://insights.sbomify.com/CVE-2023-43961/): SaToken authentication bypass vulnerability (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-44794 and fix it if it is affected.

What it is: CVE-2023-44794 is a critical vulnerability in n/a, published on 25 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-44794 exists.

Affected packages and fixed versions:
- cn.dev33:sa-token-core (Maven): affected all versions; fixed in 1.37.0
- cn.dev33:sa-token-core (Maven): affected all versions; fixed in 1.37.0

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

## Sources

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

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