prioritize_full_name_in_ux. Executing a manipulation can lead to cross site scripting.This vulnerability is tracked as CVE-2026-32607. The attack can be launched remotely. No exploit exists.
It is recommended to upgrade the affected component.
Intelligence View
⚡ tsecurity.de Intelligence
CVE-2026-32607 | Discourse up to 2026.1.2/2026.2.1 prioritize_full_name_in_ux cross site scripting
A vulnerability was found in Discourse up to 2026.1.2/2026.2.1. It has been declared as problematic. This affects the function prioritize_full_name_in_ux. Executing a manipulation can lead to cross site scripting. This vulnerability is…
Reagiere als Erste:r — dein Feedback zählt!
A vulnerability was found in Discourse up to 2026.1.2/2026.2.1. It has been declared as problematic. This affects the function
This vulnerability is tracked as CVE-2026-32607. The attack can be launched remotely. No exploit exists.
It is recommended to upgrade the affected component.
This vulnerability is tracked as CVE-2026-32607. The attack can be launched remotely. No exploit exists.
It is recommended to upgrade the affected component.
2. Cyber Threat Intelligence & Forensik
IoC Intelligence (1 Indikatoren)
CVE-2026-32607
Exploit & Remediation Lifecycle Timeline
CVE-2026-32607Entdeckung & Meldung
Schwachstelle identifiziert & registriert
Sicherheits-Advisory
Offizielle Warnung & CVE-Zuweisung
Exploit / PoC
Öffentlicher Nachweis/Code verfügbar (Exploit-DB/EUVD)
In-the-Wild Ausnutzung
Keine Massenausnutzung gemeldet
Patch & Schutzmaßnahmen
Upstream-Patch-Referenz vorhanden (Commit-/Advisory-Link)
Exploit Weaponization & Public PoC Radar
ELEVATED · Index 15/100Exploit-DB
Kein EDB-EintragInteraktion
Interaktion nötigAuthentifizierung
Erforderlich3. Compliance, SLA & Vendor Adherence
CISA-SSVC-Triage (vulnrichment)CVE-2026-32607
Exploitation: none (Keine bekannte Ausnutzung)Automatable: no (Nicht automatisierbar)Technical Impact: partial (Teilweise)
Quelle: CISA-ADP vulnrichment · Stand 2026-04-01T13:48:48.553781Z · CISA Coordinator
Advisory Radar
In herstellerseitiger Prüfung
Hersteller-Sicherheitsmeldungen & Patch-Status
Handlungsempfehlung für Administratoren
Hersteller-Advisory noch nicht formal hinterlegt. Regelmäßiges Re-Scanning der CTI-Quellen anberaumt.
Referenzen aus der Primärquelle („Verifiziert" nur bei Hersteller-Domäne):
-
Upstream-Referenz (Code-Hosting, kein Advisory)github.com
-
Upstream-Referenz (Code-Hosting, kein Advisory)github.com