CVE-2024-42515

Description

Glossarizer through 1.5.2 improperly tries to convert text into HTML. Even though the application itself escapes special characters (e.g., <>), the underlying library converts these encoded characters into legitimate HTML, thereby possibly causing stored XSS. Attackers can append a XSS payload to a word that has a corresponding glossary entry.

Severity
CRITICAL
CVSS v3
9.9
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:L · source adp
Exploit chance (EPSS)
0.474%
chance of exploitation in the next 30 days
higher than 41.6% of scored CVEs · 2026-11-17
CISA KEV
Not listed
Public exploit code
None public
Exploit references (NVD and CNA): 0
Metasploit modules: 0
Nuclei templates: 0

Weakness

CISA SSVC decision points

Exploitationpoc
Automatableyes
Technical impactpartial
Scored2024-11-01

Timeline

  1. 2024-10-31Published by the CNA00:00 UTC
  2. 2024-10-31GitHub advisory published (GHSA-hhhv-ggjx-q9j2)same day
  3. 2024-11-01CISA SSVC decision recorded1 day after publication

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Exploit and advisory records

GitHub advisory GHSA-hhhv-ggjx-q9j2, affected packages:

PackageVulnerable versionsFixed in
npm glossarizerthrough 1.5.2

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources