CVE-2026-72730

HIGHPre-NVD 8.78.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 86% 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, secondary
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.7Exploit: None knownExposed: 0

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

Discourse is an open-source discussion platform. Prior to 2026.1.6, 2026.5.2, 2026.6.1, and 2026.7.0, the Rich Text Editor rendered a chat-transcript username as HTML, allowing stored cross-site scripting. This issue is fixed in versions 2026.1.6, 2026.5.2, 2026.6.1, and 2026.7.0.

CVSS v3
8.7
EG Score
8.7(medium)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

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
Severity87% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
14%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 10, 2026

Advisory Details (5)

Auto-updated Aug 10, 2026
Patch available. Sources: github, github_commit.
github_commit

commit 9633b8ecaf5a (discourse/discourse)

Fix landed in discourse/discourse commit 9633b8ecaf5a — awaiting tagged release

https://github.com/discourse/discourse/commit/9633b8ecaf5a99f0407f5261b9bd1a05f7dac529
github_commit

commit 7eb35d076ab9 (discourse/discourse)

Fix landed in discourse/discourse commit 7eb35d076ab9 — awaiting tagged release

https://github.com/discourse/discourse/commit/7eb35d076ab9b6a612e86182336ce9787ce402ea
github_commit

commit 3fb1e8ead0d4 (discourse/discourse)

Fix landed in discourse/discourse commit 3fb1e8ead0d4 — awaiting tagged release

https://github.com/discourse/discourse/commit/3fb1e8ead0d4f48d2cf55c8110825c7e8a6a45f5
github_commit

commit 32920affe4ad (discourse/discourse)

Fix landed in discourse/discourse commit 32920affe4ad — awaiting tagged release

https://github.com/discourse/discourse/commit/32920affe4ad97b461ca2ae2f664c5fefc374baf
github Patch Available

Stored XSS chat-transcript username unescaped in Rich Text Editor · Advisory · discourse/discourse · GitHub

https://github.com/discourse/discourse/security/advisories/GHSA-wg48-qxjc-f459

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× 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-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 09:56 UTCEG score recompute
  3. 2026-08-28 21:42 UTCEPSS rescore
  4. 2026-08-27 19:42 UTCEG score recompute
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-26 18:54 UTCEG score recompute
  7. 2026-08-26 14:47 UTCEPSS rescore
  8. 2026-08-25 17:50 UTCEG score recompute
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-24 18:04 UTCEG score recompute
  11. 2026-08-23 06:07 UTCEG score recompute
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-22 06:21 UTCEG score recompute
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-21 06:35 UTCEG score recompute
  16. 2026-08-20 22:56 UTCEPSS rescore
  17. 2026-08-19 18:55 UTCEG score recompute
  18. 2026-08-19 17:04 UTCEPSS rescore
  19. 2026-08-18 19:08 UTCEG score recompute
  20. 2026-08-18 13:49 UTCEPSS rescore
  21. 2026-08-18 13:49 UTCEPSS rescore
  22. 2026-08-17 19:18 UTCEG score recompute
  23. 2026-08-17 13:47 UTCEPSS rescore
  24. 2026-08-16 18:31 UTCEG score recompute
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 15 more
  1. 2026-08-16 14:56 UTCEPSS rescore
  2. 2026-08-16 06:37 UTCEG score recompute
  3. 2026-08-16 02:15 UTCEPSS rescore
  4. 2026-08-15 06:52 UTCEG score recompute
  5. 2026-08-15 01:31 UTCEPSS rescore
  6. 2026-08-14 06:42 UTCEG score recompute
  7. 2026-08-13 22:00 UTCEPSS rescore
  8. 2026-08-12 18:59 UTCEG score recompute
  9. 2026-08-12 13:51 UTCEPSS rescore
  10. 2026-08-11 19:13 UTCEG score recompute
  11. 2026-08-10 19:27 UTCEG score recompute
  12. 2026-08-10 18:55 UTCEG score recompute
  13. 2026-08-10 17:22 UTCEG score recompute
  14. 2026-08-10 16:30 UTCEG score recompute
  15. 2026-08-10 16:29 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-72730?
CVE-2026-72730 is a high vulnerability published on August 10, 2026. Discourse is an open-source discussion platform. Prior to 2026.1.6, 2026.5.2, 2026.6.1, and 2026.7.0, the Rich Text Editor rendered a chat-transcript username as HTML, allowing stored cross-site scripting. This issue is fixed in versions 2026.1.6, 2026.5.2, 2026.6.1, and 2026.7.0.
When was CVE-2026-72730 disclosed?
CVE-2026-72730 was first published in the National Vulnerability Database on August 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72730 actively exploited?
CVE-2026-72730 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 85.5% of all scored CVEs.
What is the CVSS score of CVE-2026-72730?
CVE-2026-72730 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-72730?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72730, 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-2026-72730

Explore →

Is Your Infrastructure Affected by CVE-2026-72730?

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

Start Free Scan →Browse All CVEs