CVE-2025-24897

HIGHNVD 8.28.2
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 88% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
8.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.2Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Misskey is an open source, federated social media platform. Starting in version 12.109.0 and prior to version 2025.2.0-alpha.0, due to a lack of CSRF protection and the lack of proper security attributes in the authentication cookies of Bull's dashboard, some of the APIs of bull-board may be subject to CSRF attacks. There is a risk of this vulnerability being used for attacks with relatively large impact on availability and integrity, such as the ability to add arbitrary jobs. This vulnerability was fixed in 2025.2.0-alpha.0. As a workaround, block all access to the /queue directory with a web application firewall (WAF).

CVSS v3
8.2
EG Score
8.2(medium)
EPSS
3.1%
KEV
Not listed

Published

February 11, 2025

Last Modified

November 26, 2025

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-18 10:03 UTCEPSS rescore
  2. 2026-07-16 17:02 UTCEPSS rescore
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 16:57 UTCEPSS rescore
  5. 2026-07-13 22:29 UTCEPSS rescore
  6. 2026-07-13 22:29 UTCEPSS rescore
  7. 2026-07-12 05:46 UTCEPSS rescore
  8. 2026-07-12 05:46 UTCEPSS rescore
  9. 2026-07-11 08:27 UTCEPSS rescore
  10. 2026-07-11 08:26 UTCEPSS rescore
  11. 2026-07-09 19:09 UTCEPSS rescore
  12. 2026-07-08 15:14 UTCEPSS rescore
  13. 2026-07-07 13:45 UTCEPSS rescore
  14. 2026-07-07 11:21 UTCOSV refresh
  15. 2026-07-06 16:26 UTCEPSS rescore
  16. 2026-07-06 02:22 UTCEPSS rescore
  17. 2026-07-06 02:22 UTCEPSS rescore
  18. 2026-07-05 02:30 UTCEPSS rescore
  19. 2026-07-04 06:30 UTCEPSS rescore
  20. 2026-06-29 14:06 UTCEPSS rescore
  21. 2026-06-28 14:07 UTCEPSS rescore
  22. 2026-06-28 14:07 UTCEPSS rescore
  23. 2026-06-28 04:55 UTCEPSS rescore
  24. 2026-06-28 04:55 UTCEPSS rescore
  25. 2026-06-27 03:08 UTCEPSS rescore
Show 51 more
  1. 2026-06-27 03:08 UTCEPSS rescore
  2. 2026-06-25 13:49 UTCEPSS rescore
  3. 2026-06-25 13:49 UTCEPSS rescore
  4. 2026-06-24 14:04 UTCEPSS rescore
  5. 2026-06-24 14:04 UTCEPSS rescore
  6. 2026-06-23 21:32 UTCEPSS rescore
  7. 2026-06-23 21:32 UTCEPSS rescore
  8. 2026-06-22 14:25 UTCEPSS rescore
  9. 2026-06-22 14:25 UTCEPSS rescore
  10. 2026-06-21 14:56 UTCEPSS rescore
  11. 2026-06-21 14:56 UTCEPSS rescore
  12. 2026-06-21 01:59 UTCEPSS rescore
  13. 2026-06-21 01:59 UTCEPSS rescore
  14. 2026-06-19 19:25 UTCEPSS rescore
  15. 2026-06-19 19:25 UTCEPSS rescore
  16. 2026-06-18 22:13 UTCOSV refresh
  17. 2026-06-18 17:52 UTCEPSS rescore
  18. 2026-06-18 17:52 UTCEPSS rescore
  19. 2026-06-17 17:52 UTCEPSS rescore
  20. 2026-06-16 17:52 UTCEPSS rescore
  21. 2026-06-16 17:52 UTCEPSS rescore
  22. 2026-06-15 17:48 UTCEPSS rescore
  23. 2026-06-14 23:17 UTCEPSS rescore
  24. 2026-06-13 22:59 UTCEPSS rescore
  25. 2026-06-12 23:11 UTCEPSS rescore
  26. 2026-06-11 13:59 UTCEPSS rescore
  27. 2026-06-10 22:18 UTCEPSS rescore
  28. 2026-06-10 13:22 UTCEPSS rescore
  29. 2026-06-08 14:16 UTCEPSS rescore
  30. 2026-06-08 14:16 UTCEPSS rescore
  31. 2026-06-07 15:24 UTCEPSS rescore
  32. 2026-06-07 15:24 UTCEPSS rescore
  33. 2026-06-06 13:47 UTCEPSS rescore
  34. 2026-06-06 13:47 UTCEPSS rescore
  35. 2026-06-05 22:46 UTCEPSS rescore
  36. 2026-06-05 22:46 UTCEPSS rescore
  37. 2026-06-05 06:10 UTCEPSS rescore
  38. 2026-06-05 06:10 UTCEPSS rescore
  39. 2026-06-04 13:11 UTCEPSS rescore
  40. 2026-06-04 13:11 UTCEPSS rescore
  41. 2026-06-02 20:12 UTCEPSS rescore
  42. 2026-06-02 20:12 UTCEPSS rescore
  43. 2026-06-01 13:51 UTCEPSS rescore
  44. 2026-06-01 13:51 UTCEPSS rescore
  45. 2026-05-31 22:30 UTCEPSS rescore
  46. 2026-05-31 22:30 UTCEPSS rescore
  47. 2026-05-31 00:16 UTCEPSS rescore
  48. 2026-05-31 00:16 UTCEPSS rescore
  49. 2026-05-30 12:01 UTCEG score recompute
  50. 2026-05-29 16:50 UTCOSV refresh
  51. 2026-05-29 13:44 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-24897?
CVE-2025-24897 is a high vulnerability published on February 11, 2025. Misskey is an open source, federated social media platform. Starting in version 12.109.0 and prior to version 2025.2.0-alpha.0, due to a lack of CSRF protection and the lack of proper security attributes in the authentication cookies of Bull's dashboard, some of the APIs of bull-board may be…
When was CVE-2025-24897 disclosed?
CVE-2025-24897 was first published in the National Vulnerability Database on February 11, 2025, with the most recent update on November 26, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-24897 actively exploited?
CVE-2025-24897 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-24897?
CVE-2025-24897 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2025-24897?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-24897, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-24897

Explore →

Is Your Infrastructure Affected by CVE-2025-24897?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.