CVE-2023-22487

HIGHNVD 7.77.7
EchelonGraph scoreMEDIUM confidence

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

Score 7.7 from GitHub Security Advisory (severity: HIGH) published 2023-01-10. NVD baseline CVSS 7.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2023-0303 (ENISA EUVD) · GHSA-22m9-m3ww-53h3 (GitHub Security Advisories)Source: ENISA EUVD

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 impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity77% × 45%
Impact severity (EG Severity): CVSS 7.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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
52nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.7): severity, escalated by confirmed exploitation. This CVE's 7.7 is its impact severity (EG Severity), not escalated.

EG Severity
7.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-03). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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.

The score's inputs: 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

Advisory Details (2)

Auto-updated Oct 28, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Post mentions can be used to read any post on the forum without access control · Advisory · flarum/framework · GitHub

https://github.com/flarum/framework/security/advisories/GHSA-22m9-m3ww-53h3
GitHub commit

commit ab1c868b978e (flarum/framework)

Fix landed in flarum/framework commit ab1c868b978e — awaiting tagged release

https://github.com/flarum/framework/commit/ab1c868b978e8b0d09a5d682c54665dae17d0985

Vendor Advisories for CVE-2023-22487(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
composerflarum/mentions @ 1.6.3 (fixes < 1.6.3)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

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 11× in last 7d / 41× 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 98 of 222 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 124 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-03 22:45 UTCEG score recompute
  2. 2026-11-03 22:45 UTCGHSA enrichmentGHSA-22m9-m3ww-53h3 · GitHub severity HIGH · GitHub CVSS 7.7
  3. 2026-11-03 16:40 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  4. 2026-11-02 16:39 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  5. 2026-11-01 16:30 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  6. 2026-11-01 08:22 UTCGHSA enrichmentGHSA-22m9-m3ww-53h3 · GitHub severity HIGH · GitHub CVSS 7.7
  7. 2026-11-01 08:22 UTCEG score recompute
  8. 2026-10-31 16:29 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  9. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  10. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  11. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  12. 2026-10-28 05:38 UTCEG score recompute
  13. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  14. 2026-10-26 16:28 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  15. 2026-10-25 17:49 UTCEG score recompute
  16. 2026-10-25 16:29 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  17. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  18. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  19. 2026-10-22 16:30 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  20. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  21. 2026-10-21 04:58 UTCEG score recompute
  22. 2026-10-20 16:29 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  23. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  24. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  25. 2026-10-18 08:13 UTCEG score recompute
Show 73 more
  1. 2026-10-17 16:29 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  2. 2026-10-16 16:35 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  3. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  4. 2026-10-15 02:54 UTCOSV refresh
  5. 2026-10-14 16:29 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  6. 2026-10-13 16:29 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  7. 2026-10-12 18:36 UTCEG score recompute
  8. 2026-10-12 16:30 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  9. 2026-10-11 21:59 UTCEG score recompute
  10. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  11. 2026-10-10 19:57 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  12. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  13. 2026-10-08 17:05 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  14. 2026-10-07 23:45 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  15. 2026-10-06 15:14 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  16. 2026-10-05 17:40 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  17. 2026-10-04 23:19 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  18. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  19. 2026-10-02 16:23 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  20. 2026-10-01 19:47 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  21. 2026-09-30 16:17 UTCEG score recompute
  22. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  23. 2026-09-29 15:16 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  24. 2026-09-26 15:55 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  25. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  26. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  27. 2026-09-24 00:36 UTCOSV refresh
  28. 2026-09-23 13:45 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  29. 2026-09-22 14:45 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  30. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  31. 2026-09-19 15:38 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  32. 2026-09-18 19:25 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  33. 2026-09-17 19:24 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  34. 2026-09-16 14:05 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  35. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  36. 2026-09-15 03:07 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  37. 2026-09-13 16:44 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  38. 2026-09-12 14:58 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  39. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  40. 2026-09-08 21:57 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  41. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  42. 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  43. 2026-09-05 15:25 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  44. 2026-09-04 18:29 UTCOSV refresh
  45. 2026-09-04 13:57 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  46. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  47. 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  48. 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  49. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  50. 2026-08-30 01:19 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  51. 2026-08-28 21:38 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  52. 2026-08-27 14:22 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  53. 2026-08-26 14:43 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  54. 2026-08-25 13:46 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  55. 2026-08-24 14:14 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  56. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  57. 2026-08-21 23:46 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  58. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  59. 2026-08-19 17:01 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  60. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  61. 2026-08-18 05:52 UTCOSV refresh
  62. 2026-08-17 13:44 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  63. 2026-08-16 14:53 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  64. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  65. 2026-08-15 01:27 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  66. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  67. 2026-08-12 13:48 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  68. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  69. 2026-08-08 16:34 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  70. 2026-08-07 16:24 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  71. 2026-08-06 13:44 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  72. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  73. 2026-08-04 15:07 UTCEPSS rescoreEPSS 0.7% · 48th 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 (52nd 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. The vendor advisories EchelonGraph has for CVE-2023-22487 are linked in the Vendor Advisories panel on this page.

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