CVE-2019-19999

HIGHNVD 7.27.2—

7.2

Halo before 1.2.0-beta.1 allows Server Side Template Injection (SSTI) because TemplateClassResolver.SAFER_RESOLVER is not used in the FreeMarker configuration.

CVSS v3: 7.2
EG Score: 7.2(medium)
EPSS: 62.0%
KEV: Not listed

Published

December 26, 2019

Last Modified

November 21, 2024

References (6)

cve@mitrehttps://github.com/halo-dev/halo/compare/v1.1.3-beta.2...v1.2.0-beta.1
cve@mitrehttps://github.com/halo-dev/halo/issues/419
cve@mitrehttps://github.com/halo-dev/halo/issues/440
af854a3a-2127-422b-91ae-364da2661108https://github.com/halo-dev/halo/compare/v1.1.3-beta.2...v1.2.0-beta.1
af854a3a-2127-422b-91ae-364da2661108https://github.com/halo-dev/halo/issues/419
af854a3a-2127-422b-91ae-364da2661108https://github.com/halo-dev/halo/issues/440

Weakness Classification(1)

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

CWE-918Server-Side Request Forgery (SSRF)

Data Freshness Timeline

(refreshed 10× in last 7d / 18× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:42 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-27 09:55 UTCEG score recompute
2026-05-27 09:55 UTCGHSA enrichment
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch

Frequently asked(5)

What is CVE-2019-19999?

CVE-2019-19999 is a high vulnerability published on December 26, 2019. Halo before 1.2.0-beta.1 allows Server Side Template Injection (SSTI) because TemplateClassResolver.SAFER_RESOLVER is not used in the FreeMarker configuration.

When was CVE-2019-19999 disclosed?

CVE-2019-19999 was first published in the National Vulnerability Database on December 26, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2019-19999 actively exploited?

CVE-2019-19999 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 62.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2019-19999?

CVE-2019-19999 has a CVSS v3 base score of 7.2 (NVD).

How do I remediate CVE-2019-19999?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-19999, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-19999

Explore →

Is Your Infrastructure Affected by CVE-2019-19999?

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

Start Free Scan →Browse All CVEs

CVE-2019-19999

📅 Published

🔄 Last Modified

🔗 References (6)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2019-19999?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (6)

Frequently asked(5)

Related CVEs(same CWE)