# CVE-2023-52139: Misskey vulnerable to improper authorization when accessing with third-party application

> Third-party apps can access unauthorized endpoints to leak secrets or create invitations, requiring a patch to Misskey.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-7pxq-6xx9-xpgm

## What is CVE-2023-52139?

CVE-2023-52139 is a critical missing authorization vulnerability in misskey-dev misskey, published on 29 Dec 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Misskey is an open source, decentralized social media platform. Third-party applications may be able to access some endpoints or Websocket APIs that are incorrectly specified as [kind](https://github.com/misskey-dev/misskey/blob/406b4bdbe79b5b0b68fcdcb3c4b6e419460a0258/packages/backend/src/server/api/endpoints.ts#L811) or [secure](https://github.com/misskey-dev/misskey/blob/406b4bdbe79b5b0b68fcdcb3c4b6e419460a0258/packages/backend/src/server/api/endpoints.ts#L805) without the user's permission and perform operations such as reading or adding non-public content. As a result, if the user who authenticated the application is an administrator, confidential information such as object storage secret keys and SMTP server passwords will be leaked, and general users can also create invitation codes without permission and leak non-public user information. This is patched in version [2023.12.1](https://github.com/misskey-dev/misskey/commit/c96bc36fedc804dc840ea791a9355d7df0748e64).

Weakness: CWE-285 (Improper Authorization)

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

It affects 1 product.


Products: Misskey Misskey.

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

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

## Is CVE-2023-52139 being exploited?

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

## Other vulnerabilities in misskey-dev misskey

- [CVE-2025-25306](https://insights.sbomify.com/CVE-2025-25306/): Misskey's Incomplete Patch of CVE-2024-52591 Leads to Forgery of Federated Notes (critical 9.3)
- [CVE-2023-49079](https://insights.sbomify.com/CVE-2023-49079/): Misskey's missing signature validation allows arbitrary users to impersonate any remote user. (critical 9.3)
- [CVE-2026-28431](https://insights.sbomify.com/CVE-2026-28431/): Misskey lacks proper authorization checks and input validation (critical 9.2)
- [CVE-2024-52590](https://insights.sbomify.com/CVE-2024-52590/): Missing validation allows spoofed profiles in Misskey (high 8.8)
- [CVE-2024-52591](https://insights.sbomify.com/CVE-2024-52591/): Missing validation allows spoofed profiles and notes in Misskey (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-52139 is a critical missing authorization vulnerability in misskey-dev misskey, published on 29 Dec 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-52139 in the wild and no public exploit code.

Affected product: misskey-dev misskey. 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-52139/ (Markdown: https://insights.sbomify.com/CVE-2023-52139/index.md)
```

## Sources

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

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