# CVE-2024-40465: Beego privilege escalation vulnerability

> A remote attacker can escalate privileges in the beego Go web framework due to weak cryptographic practices in cache file naming.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 31 Jul 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-wr3p-r5fj-wf97

## What is CVE-2024-40465?

CVE-2024-40465 is a high-severity vulnerability in n/a, published on 31 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue in beego v.2.2.0 and before allows a remote attacker to escalate privileges via the getCacheFileName function in file.go file

Weakness: CWE-328 (Use of Weak Hash), CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

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

2 open source packages ship an affected version, including github.com/beego/beego/v2. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/beego/beego/v2` | Go | All versions | 2.2.1 |
| `github.com/beego/beego/v2` | Go | All versions | 2.2.1 |

Products: Beego Beego.

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

Upgrade github.com/beego/beego/v2 to 2.2.1 or later.

## Is CVE-2024-40465 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-31836](https://insights.sbomify.com/CVE-2022-31836/): Path Traversal in Beego (critical 9.8)
- [CVE-2022-31259](https://insights.sbomify.com/CVE-2022-31259/): Access control bypass in beego (critical 9.8)
- [CVE-2021-30080](https://insights.sbomify.com/CVE-2021-30080/): Access control bypass in Beego (critical 9.8)
- [CVE-2025-30223](https://insights.sbomify.com/CVE-2025-30223/): Beego allows Reflected/Stored XSS in Beego's RenderForm() Function Due to Unescaped User Input (critical 9.3)
- [CVE-2024-40464](https://insights.sbomify.com/CVE-2024-40464/): Beego privilege escalation vulnerability (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-40465 is a high-severity vulnerability in n/a, published on 31 Jul 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-40465 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/beego/beego/v2 (Go): affected all versions; fixed in 2.2.1
- github.com/beego/beego/v2 (Go): affected all versions; fixed in 2.2.1

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

## Sources

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

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