CVE-2017-8384

MEDIUMNVD 6.16.1—

6.1

Craft CMS before 2.6.2976 allows XSS attacks because an array returned by HttpRequestService::getSegments() and getActionSegments() need not be zero-based. NOTE: this vulnerability exists because of an incomplete fix for CVE-2017-8052.

CVSS v3: 6.1
EG Score: 6.1(medium)
EPSS: 54.2%
KEV: Not listed

Published

May 1, 2017

Last Modified

May 13, 2026

References (4)

cve@mitrehttps://craftcms.com/changelog#2-6-2976
cve@mitrehttps://twitter.com/CraftCMS/status/857743080224473088
af854a3a-2127-422b-91ae-364da2661108https://craftcms.com/changelog#2-6-2976
af854a3a-2127-422b-91ae-364da2661108https://twitter.com/CraftCMS/status/857743080224473088

Affected Packages

(1 across 1 ecosystem)

Packagist(1)

Package	Vulnerable range	Fixed in	Dependents
craftcms/cms	1.0.26.1 ... 2.6.2975 (278 versions)	2.6.2976	—

Data Freshness Timeline

(refreshed 10× in last 7d / 20× 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:49 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:41 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-27 13:38 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-23 00:10 UTCEG score recompute
2026-05-22 21:15 UTCepss_batch
2026-05-22 21:15 UTCepss_batch
2026-05-22 21:15 UTCepss_batch
2026-05-22 21:15 UTCepss_batch

Frequently asked(5)

What is CVE-2017-8384?

CVE-2017-8384 is a medium vulnerability published on May 1, 2017. Craft CMS before 2.6.2976 allows XSS attacks because an array returned by HttpRequestService::getSegments() and getActionSegments() need not be zero-based. NOTE: this vulnerability exists because of an incomplete fix for CVE-2017-8052.

When was CVE-2017-8384 disclosed?

CVE-2017-8384 was first published in the National Vulnerability Database on May 1, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2017-8384 actively exploited?

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

What is the CVSS score of CVE-2017-8384?

CVE-2017-8384 has a CVSS v3 base score of 6.1 (NVD).

How do I remediate CVE-2017-8384?

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

Explore →

Is Your Infrastructure Affected by CVE-2017-8384?

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

Start Free Scan →Browse All CVEs

CVE-2017-8384

📅 Published

🔄 Last Modified

🔗 References (4)