CVE-2023-22487

HIGHNVD 7.77.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.7 under NVD CVSS v3. EPSS exploit probability: 0.7% (50th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this weekElevated
7.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.7Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.7HIGHmedium confidence
EG Risk
51
EG Risk 51/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity77% × 45%
The EG Score, 7.7 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
50th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

January 11, 2023

Last Modified

November 21, 2024

References (2)

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
flarum/mentionsv0.1.0-beta.10 ... v1.6.1 (25 versions)
  • every version up to 1.6.3: fixed in 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 / 33× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 90 of 187 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 10 repeat rows among the latest 100 are merged into the row they repeat. The 97 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-22487?
CVE-2023-22487 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2023-22487 published?
The CVE record for CVE-2023-22487 was published on January 11, 2023. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2023-22487 actively exploited?
CVE-2023-22487 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
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?
A fix for CVE-2023-22487 is available: update to the fixed version the vendor names in its advisory.

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.

Book a Demo →Browse All CVEs