# CVE-2022-31259: Access control bypass in beego

> Attackers can bypass access control in beego web framework by appending .xml to route segments, allowing unauthorized access to protected resources.

- **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:** 21 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-qx32-f6g6-fcfr, GO-2022-0463

## What is CVE-2022-31259?

CVE-2022-31259 is a critical authentication bypass vulnerability in n/a, published on 21 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The route lookup process in beego before 1.12.9 and 2.x before 2.0.3 allows attackers to bypass access control. When a /p1/p2/:name route is configured, attackers can access it by appending .xml in various places (e.g., p1.xml instead of p1).

## Which versions are affected by CVE-2022-31259?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/beego/beego` | Go | All versions | 1.12.9 |
| `github.com/beego/beego` | Go | All versions | 1.12.9 |
| `github.com/beego/beego` | Go | All versions | 1.12.9 |
| `github.com/astaxie/beego` | Go | All versions | None |
| `github.com/beego/beego/v2` | Go | All versions | 2.0.3 |
| `github.com/beego/beego/v2` | Go | All versions | 2.0.3 |
| `github.com/beego/beego/v2` | Go | All versions | 2.0.3 |

Products: Beego Beego.

## How do I fix CVE-2022-31259?

Upgrade github.com/beego/beego to 1.12.9 or later.

## Is CVE-2022-31259 being exploited?

There is no known exploitation of CVE-2022-31259 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-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)
- [CVE-2024-40465](https://insights.sbomify.com/CVE-2024-40465/): Beego privilege escalation vulnerability (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-31259 and fix it if it is affected.

What it is: CVE-2022-31259 is a critical authentication bypass vulnerability in n/a, published on 21 May 2022. 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-2022-31259 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/beego/beego (Go): affected all versions; fixed in 1.12.9
- github.com/beego/beego (Go): affected all versions; fixed in 1.12.9
- github.com/beego/beego (Go): affected all versions; fixed in 1.12.9
- github.com/astaxie/beego (Go): affected all versions; no fix listed
- github.com/beego/beego/v2 (Go): affected all versions; fixed in 2.0.3
- github.com/beego/beego/v2 (Go): affected all versions; fixed in 2.0.3
- github.com/beego/beego/v2 (Go): affected all versions; fixed in 2.0.3

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

## Sources

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

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