CVE-2023-24810
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMisskey is an open source, decentralized social media platform. Due to insufficient validation of the redirect URL during `miauth` authentication in Misskey, arbitrary JavaScript can be executed when a user allows the link. All versions below 13.3.1 (including 12.x) are affected. This has been fixed in version 13.3.1. Users are advised to upgrade. Users unable to upgrade should not allow authentication of untrusted apps.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMisskey's miauth authentication mechanism does not properly validate redirect URLs, allowing attackers to inject arbitrary JavaScript through malicious redirect links. This enables stored XSS when users authenticate to untrusted applications.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 13.3.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Misskey is installedIdentify if the web application running is Misskey. This may be visible in the application UI, in process lists, or by examining running services. Check the application's title page, footer, or meta information for 'Misskey' branding.Affected if The system is running Misskey as the social media platform
-
Determine installed Misskey versionCheck the version of Misskey currently running. This is typically displayed in the application footer, admin dashboard, or can be found in package.json, version file, or by querying the instance's API endpoints if available.Affected if The installed version is any version prior to 13.3.1 (e.g., 13.3.0, 13.2.x, or earlier)
-
Verify miauth authentication is accessibleDetermine if the miauth authentication endpoint is available on the instance. This is typically accessed at /miauth or similar endpoints used for third-party application authentication. Check if the instance allows or has historically allowed external applications to request user authentication.Affected if The miauth endpoint is accessible and the instance permits third-party application authentication requests
-
Review granted application permissionsAudit any third-party applications that have been granted authentication permissions through miauth. Check for applications that may be untrusted or were granted permissions unexpectedly.Affected if Any untrusted or suspicious third-party applications have been authorized through the misskey instance's authentication system
A user is affected if they are running any Misskey version prior to 13.3.1 and the miauth authentication mechanism is accessible to external applications.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped13.3.1
Upgrade Misskey to version 13.3.1 or later. If upgrading is not possible, avoid granting authentication permissions to untrusted third-party applications.
13.3.1
- Ensure you have a backup of your Misskey instance data and configuration
- Stop the Misskey service
- Update to version 13.3.1 using your package manager or by pulling the updated Docker image/clone the updated repository
- Run any necessary database migrations if required by the version upgrade
- Restart the Misskey service
- Verify the instance is running correctly and the miauth functionality works as expected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-24810 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-24810 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data