# CVE-2023-31726: Missing authorization in n/a

> Attackers can exploit incorrect access control in AList to obtain sensitive information without proper authorization.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 May 2023
- **Updated:** 21 Jan 2025
- **Also known as:** GHSA-rq2h-mjp2-vqpr

## What is CVE-2023-31726?

CVE-2023-31726 is a high-severity missing authorization vulnerability in n/a, published on 23 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

AList 3.15.1 is vulnerable to Incorrect Access Control, which can be exploited by attackers to obtain sensitive information.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Alistgo Alist.

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

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

## Is CVE-2023-31726 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-45969](https://insights.sbomify.com/CVE-2022-45969/): Alist vulnerable to Path Traversal (critical 9.8)
- [CVE-2026-25160](https://insights.sbomify.com/CVE-2026-25160/): Alist has Insecure TLS Config (critical 9.1)
- [CVE-2026-25161](https://insights.sbomify.com/CVE-2026-25161/): Alist vulnerable to Path Traversal in multiple file operation handlers (high 8.8)
- [CVE-2023-33498](https://insights.sbomify.com/CVE-2023-33498/): alist Incorrect Access Control vulnerability (high 8.8)
- [CVE-2022-45968](https://insights.sbomify.com/CVE-2022-45968/): AList vulnerable to Improper Preservation of Permissions (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-31726 is a high-severity missing authorization vulnerability in n/a, published on 23 May 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-31726 exists.

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

## Sources

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

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