CVE-2023-22487

HIGHNVD 7.77.7
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.7 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 57% 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
7.7
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.7Exploit: NoneExposed: 0

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

Flarum is a forum software for building communities. Using the mentions feature provided by the flarum/mentions extension, users can mention any post ID on the forum with the special @""#p syntax. The following behavior never changes no matter if the actor should be able to read the mentioned post or not: A URL to the mentioned post is inserted into the actor post HTML, leaking its discussion ID and post number. The mentionsPosts relationship included in the POST /api/posts and PATCH /api/posts/ JSON responses leaks the full JSON:API payload of all mentioned posts without any access control. This includes the content, date, number and attributes added by other extensions. An attacker only needs the ability to create new posts on the forum to exploit the vulnerability. This works even if new posts require approval. If they have the ability to edit posts, the attack can be performed even more discreetly by using a single post to scan any size of database and hiding the attack post content afterward. The attack allows the leaking of all posts in the forum database, including posts awaiting approval, posts in tags the user has no access to, and private discussions created by other extensions like FriendsOfFlarum Byobu. This also includes non-comment posts like tag changes or renaming events. The discussion payload is not leaked but using the mention HTML payload it's possible to extract the discussion ID of all posts and combine all posts back together into their original discussions even if the discussion title remains unknown. All Flarum versions prior to 1.6.3 are affected. The vulnerability has been fixed and published as flarum/core v1.6.3. As a workaround, user can disable the mentions extension.

CVSS v3
7.7
EG Score
7.7(medium)
EPSS
47.5%
KEV
Not listed

Published

January 11, 2023

Last Modified

November 21, 2024

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFixed inDependents
flarum/mentionsv0.1.0-beta.10 ... v1.6.1 (25 versions)1.6.3

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 48× 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-12 05:45 UTCEPSS rescore
  2. 2026-07-12 05:45 UTCEPSS rescore
  3. 2026-07-11 08:25 UTCEPSS rescore
  4. 2026-07-11 08:25 UTCEPSS rescore
  5. 2026-07-09 19:08 UTCEPSS rescore
  6. 2026-07-08 15:13 UTCEPSS rescore
  7. 2026-07-07 13:44 UTCEPSS rescore
  8. 2026-07-06 16:26 UTCEPSS rescore
  9. 2026-07-06 16:25 UTCEPSS rescore
  10. 2026-07-06 02:21 UTCEPSS rescore
  11. 2026-07-05 02:28 UTCEPSS rescore
  12. 2026-07-04 06:29 UTCEPSS rescore
  13. 2026-07-04 06:29 UTCEPSS rescore
  14. 2026-07-02 16:58 UTCEPSS rescore
  15. 2026-07-01 15:04 UTCEPSS rescore
  16. 2026-06-30 23:21 UTCEPSS rescore
  17. 2026-06-29 14:04 UTCEPSS rescore
  18. 2026-06-28 14:06 UTCEPSS rescore
  19. 2026-06-28 14:06 UTCEPSS rescore
  20. 2026-06-28 08:52 UTCOSV refresh
  21. 2026-06-28 04:54 UTCEPSS rescore
  22. 2026-06-28 04:54 UTCEPSS rescore
  23. 2026-06-27 03:07 UTCEPSS rescore
  24. 2026-06-25 13:48 UTCEPSS rescore
  25. 2026-06-25 13:48 UTCEPSS rescore
Show 63 more
  1. 2026-06-24 14:03 UTCEPSS rescore
  2. 2026-06-24 14:03 UTCEPSS rescore
  3. 2026-06-23 21:31 UTCEPSS rescore
  4. 2026-06-23 21:31 UTCEPSS rescore
  5. 2026-06-22 14:24 UTCEPSS rescore
  6. 2026-06-22 14:24 UTCEPSS rescore
  7. 2026-06-21 14:55 UTCEPSS rescore
  8. 2026-06-21 14:55 UTCEPSS rescore
  9. 2026-06-21 01:58 UTCEPSS rescore
  10. 2026-06-21 01:58 UTCEPSS rescore
  11. 2026-06-19 19:24 UTCEPSS rescore
  12. 2026-06-19 19:24 UTCEPSS rescore
  13. 2026-06-18 17:51 UTCEPSS rescore
  14. 2026-06-18 17:51 UTCEPSS rescore
  15. 2026-06-17 17:51 UTCEPSS rescore
  16. 2026-06-17 17:51 UTCEPSS rescore
  17. 2026-06-16 17:51 UTCEPSS rescore
  18. 2026-06-16 17:51 UTCEPSS rescore
  19. 2026-06-16 17:51 UTCEPSS rescore
  20. 2026-06-15 17:47 UTCEPSS rescore
  21. 2026-06-14 23:16 UTCEPSS rescore
  22. 2026-06-13 22:59 UTCEPSS rescore
  23. 2026-06-12 23:10 UTCEPSS rescore
  24. 2026-06-11 13:59 UTCEPSS rescore
  25. 2026-06-11 13:58 UTCEPSS rescore
  26. 2026-06-10 22:17 UTCEPSS rescore
  27. 2026-06-10 19:17 UTCOSV refresh
  28. 2026-06-10 13:21 UTCEPSS rescore
  29. 2026-06-10 13:21 UTCEPSS rescore
  30. 2026-06-08 14:15 UTCEPSS rescore
  31. 2026-06-08 14:15 UTCEPSS rescore
  32. 2026-06-07 15:23 UTCEPSS rescore
  33. 2026-06-07 15:23 UTCEPSS rescore
  34. 2026-06-06 13:46 UTCEPSS rescore
  35. 2026-06-06 13:46 UTCEPSS rescore
  36. 2026-06-05 22:46 UTCEPSS rescore
  37. 2026-06-05 22:46 UTCEPSS rescore
  38. 2026-06-05 22:46 UTCEPSS rescore
  39. 2026-06-05 06:09 UTCEPSS rescore
  40. 2026-06-05 06:09 UTCEPSS rescore
  41. 2026-06-04 13:11 UTCEPSS rescore
  42. 2026-06-04 13:11 UTCEPSS rescore
  43. 2026-06-02 20:12 UTCEPSS rescore
  44. 2026-06-02 20:12 UTCEPSS rescore
  45. 2026-06-02 20:12 UTCEPSS rescore
  46. 2026-06-01 13:51 UTCEPSS rescore
  47. 2026-06-01 13:50 UTCEPSS rescore
  48. 2026-05-31 22:29 UTCEPSS rescore
  49. 2026-05-31 22:29 UTCEPSS rescore
  50. 2026-05-31 22:29 UTCEPSS rescore
  51. 2026-05-31 00:15 UTCEPSS rescore
  52. 2026-05-31 00:15 UTCEPSS rescore
  53. 2026-05-29 13:43 UTCEPSS rescore
  54. 2026-05-29 13:43 UTCEPSS rescore
  55. 2026-05-28 13:43 UTCEPSS rescore
  56. 2026-05-28 13:43 UTCEPSS rescore
  57. 2026-05-27 13:39 UTCEPSS rescore
  58. 2026-05-26 13:43 UTCEPSS rescore
  59. 2026-05-26 13:43 UTCEPSS rescore
  60. 2026-05-26 07:18 UTCEPSS rescore
  61. 2026-05-26 07:17 UTCEPSS rescore
  62. 2026-05-26 07:17 UTCEPSS rescore
  63. 2026-05-25 08:50 UTCEG score recompute

Frequently asked(5)

What is CVE-2023-22487?
CVE-2023-22487 is a high vulnerability published on January 11, 2023. Flarum is a forum software for building communities. Using the mentions feature provided by the flarum/mentions extension, users can mention any post ID on the forum with the special @"<username>"#p<id> syntax. The following behavior never changes no matter if the actor should be able to read the…
When was CVE-2023-22487 disclosed?
CVE-2023-22487 was first published in the National Vulnerability Database on January 11, 2023, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-22487 actively exploited?
CVE-2023-22487 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 47.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2023-22487?
CVE-2023-22487 has a CVSS v3 base score of 7.7 (NVD).
How do I remediate CVE-2023-22487?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-22487, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-22487

Explore →

Is Your Infrastructure Affected by CVE-2023-22487?

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