CVE-2023-52139Known exploitationPublic exploitNetwork attack vector

Authenticated protected-data access via unchecked app permissions

Published Dec 29, 2023 · Updated Aug 2, 2024

Improper authorization in Misskey before 2023.12.1 allows remote authenticated users to read or alter protected data through third-party applications. The API authorization service trusted endpoint metadata and allowed endpoints or WebSocket channels marked kind or secure to bypass the application's granted permissions. Exploitation requires an authenticated user's application token and user interaction to authorize that application; administrator tokens can expose object-storage and SMTP secrets, while ordinary users can create invitation codes or disclose non-public user information.

CVSS severity9.6
Critical
EPSS probability0.55%
Next 30 days · Sep 16, 2026
Known exploitationReported
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper authorization in Misskey before 2023.12.1 allows remote authenticated users to read or alter protected data through third-party applications. The API authorization service trusted endpoint metadata and allowed endpoints or WebSocket channels marked kind or secure to bypass the application's granted permissions. Exploitation requires an authenticated user's application token and user interaction to authorize that application; administrator tokens can expose object-storage and SMTP secrets, while ordinary users can create invitation codes or disclose non-public user information.

The record

CVE
CVE-2023-52139
Published
Dec 29, 2023
Updated
Aug 2, 2024
Vendor
Misskey Project
Product
Misskey
Classifications
CWE-285, CAPEC-1, T1190
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Dec 29, 2023CVE publishedPublication date reported by the CVE source.
  2. Aug 2, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 2023.12.1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Misskey Project · Misskeyversion=< 2023.12.1

Published CVSS scores

9.0GitHub, Inc.CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
9.6NVDCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationReported
Public exploitPublished

Weakness, pattern, technique

CWE-285Improper Authorization
CAPEC-1Exploit Public-Facing Application
T1190Exploit Public-Facing Application

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Reported exploitation

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo