CVE-2026-61696

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.3 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
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.3Exploit: None knownExposed: 0

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

Forem is open source software for building communities. In versions before commit 92eacd16a82cf9007ba8e16a2258b42e3b53ca9c, a malicious value submitted through feedback_message[message] is stored without sanitization and rendered in app/views/admin/feedback_messages/_feedback_message.html.erb through raw(feedback_message.message) when offender_id is present. Viewing the abuse report executes arbitrary JavaScript in an administrator's browser and may expose sensitive in-page data, abuse CSRF tokens, or perform administrative actions in the victim's session. The public FeedbackMessagesController accepts the report without authorization and previously permitted a submitted offender_id, making the vulnerable rendering path reachable by an unauthenticated attacker. This issue is fixed in commit 92eacd16a82cf9007ba8e16a2258b42e3b53ca9c

CVSS v3
6.3
EG Score
6.3(medium)
EG Risk
33(Track)
EG Risk 33/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
Severity63% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
14%
KEV
Not listed

Published

August 18, 2026

Last Modified

August 18, 2026

Advisory Details (2)

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

commit 92eacd16a82c (forem/forem)

Fix landed in forem/forem commit 92eacd16a82c — awaiting tagged release

https://github.com/forem/forem/commit/92eacd16a82cf9007ba8e16a2258b42e3b53ca9c
github Patch Available

Stored XSS in Admin Abuse Report Rendering · Advisory · forem/forem · GitHub

https://github.com/forem/forem/security/advisories/GHSA-4463-499m-94mx

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 12× 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-26 09:00 UTCEG score recompute
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-25 07:04 UTCEG score recompute
  4. 2026-08-23 03:11 UTCEG score recompute
  5. 2026-08-23 00:19 UTCEPSS rescore
  6. 2026-08-20 23:18 UTCEG score recompute
  7. 2026-08-20 22:55 UTCEPSS rescore
  8. 2026-08-19 21:22 UTCEG score recompute
  9. 2026-08-19 17:04 UTCEPSS rescore
  10. 2026-08-18 18:22 UTCEG score recompute
  11. 2026-08-18 18:07 UTCEG score recompute
  12. 2026-08-18 18:04 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-61696?
CVE-2026-61696 is a medium vulnerability published on August 18, 2026. Forem is open source software for building communities. In versions before commit 92eacd16a82cf9007ba8e16a2258b42e3b53ca9c, a malicious value submitted through feedbackmessage[message] is stored without sanitization and rendered in app/views/admin/feedbackmessages/feedbackmessage.html.erb through…
When was CVE-2026-61696 disclosed?
CVE-2026-61696 was first published in the National Vulnerability Database on August 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-61696 actively exploited?
CVE-2026-61696 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 86.4% of all scored CVEs.
What is the CVSS score of CVE-2026-61696?
CVE-2026-61696 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-61696?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-61696, 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-61696

Explore →

Is Your Infrastructure Affected by CVE-2026-61696?

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