ghsa-496g-mmpw-j9x3
Vulnerability from github
Published
2025-12-15 20:55
Modified
2025-12-20 02:26
Summary
misskey.js's export data contains private post data
Details

Summary

After adding private posts (followers, direct) that you do not have permission to view to your favorites or clips, you can export them to view the contents of the private posts.

PoC

  1. Create an account (X) for testing and an account (Y) for private posts on the same server.
  2. Send appropriate content from Y using "Follow"
  3. Send appropriate content to any user using "Nominate" from Y
  4. Obtain the URLs for the two posts above using Y's account.
  5. Query the URLs for the two posts using X and add them to your favorites or clips.
  6. Export your favorites or clips using X.
  7. Check the exported data.

Note: Verified in v2025.11.1

Impact

This could allow an attacker to view the contents of private posts. If you have pinned private posts, this could be a real problem, as the ID of the private post can be obtained by viewing the user page on the original server.

Show details on source website


{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "misskey-js"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "13.0.0-beta.16"
            },
            {
              "fixed": "2025.12.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2025-66402"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2025-12-15T20:55:27Z",
    "nvd_published_at": "2025-12-16T00:16:02Z",
    "severity": "HIGH"
  },
  "details": "### Summary\n\nAfter adding private posts (followers, direct) that you do not have permission to view to your favorites or clips, you can export them to view the contents of the private posts.\n\n### PoC\n\n1. Create an account (X) for testing and an account (Y) for private posts on the same server.\n2. Send appropriate content from Y using \"Follow\"\n3. Send appropriate content to any user using \"Nominate\" from Y\n4. Obtain the URLs for the two posts above using Y\u0027s account.\n5. Query the URLs for the two posts using X and add them to your favorites or clips.\n6. Export your favorites or clips using X.\n7. Check the exported data.\n\nNote: Verified in v2025.11.1\n\n### Impact\n\nThis could allow an attacker to view the contents of private posts.\nIf you have pinned private posts, this could be a real problem, as the ID of the private post can be obtained by viewing the user page on the original server.",
  "id": "GHSA-496g-mmpw-j9x3",
  "modified": "2025-12-20T02:26:22Z",
  "published": "2025-12-15T20:55:27Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/misskey-dev/misskey/security/advisories/GHSA-496g-mmpw-j9x3"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-66402"
    },
    {
      "type": "WEB",
      "url": "https://github.com/misskey-dev/misskey/commit/dc77d59f8712d3fe0b73cd4af2035133839cd57b"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/misskey-dev/misskey"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "misskey.js\u0027s export data contains private post data"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.


Loading…

Loading…