Skip to main content
VulnerabilityPublished

CVE-2026-73374: A stored cross-site scripting (XSS) vulnerability existed in Vulnerability-Lookup in the render_tag_badges Jinja filter used to display reference

Source GCVE Database

0
Compare

Not known to be exploited · CVSS 6.1 Medium.

Data as of 10 Nov 2026, 23:24 UTC

CVSS 4.0 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.

What to do

AI-suggested

The vulnerability was corrected by applying markupsafe.escape() to user-supplied reference tags before rendering. Until an official fix is confirmed and applied, restrict permissions to create or modify vulnerability records to trusted users only and monitor for suspicious input. Avoid visiting or sharing affected pages if exploitation is suspected.

Description

A stored cross-site scripting (XSS) vulnerability was present in the Vulnerability-Lookup application within the render_tag_badges Jinja filter. This flaw allowed authenticated users with permissions to create or modify vulnerability records to inject arbitrary HTML or JavaScript into reference tags. The injected code would be stored and later rendered without proper escaping on public vulnerability pages, potentially executing scripts in the context of any visitor's browser. The vulnerability was fixed by properly escaping user-supplied tags before rendering.

References

Community reviews

Loading reviews…