Content Security Policy appears to be missing in software and production setup

published 2024-12-12 22 mo ago modified 2026-06-17 4 mo ago also EUVD-2024-52842

cvss: 7.1; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 24%
public exploits: 0; none known

Hush Line is an open-source whistleblower management system. Starting in version 0.1.0 and prior to version 0.3.5, the productions server appeared to have been misconfigured and missed providing any content security policy or security headers. This could result in bypassing of cross-site scripting filters. Version 0.3.5 fixed the issue.

Patch / fix

fixed in 1

hushline hush_line 0.3.5

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 22 mo ago (2024-12-13)

Exploit prediction

0.31% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	7.1	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

Affected products

scidsg hushline

Classification

Weakness

CWE-1021 Improper Restriction of Rendered UI Layers or Frames

References

github.com /scidsg/hushline/security/advisories/GHSA-m592-g8qv-hrqx

Sources

CVE List CVE-2024-55888
NVD CVE-2024-55888

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.

Summary