Skip to content
Fencer Intel
medium 6.1

CVE-2017-7725 json

Concrete CMS vulnerable to cross-site scripting (XSS)

published 2017-04-13 9 y ago modified 2026-06-17 4 mo ago also GHSA-2mvg-c6mg-3q63 , EUVD-2022-2017

cvss
6.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.8%
EPSS 2.8% chance of exploitation in 30 days, percentile 86%
public exploits
1
Exploit-DB

Summary

concrete5 8.1.0 places incorrect trust in the HTTP Host header during caching, if the administrator did not define a "canonical" URL on installation of concrete5 using the "Advanced Options" settings. Remote attackers can make a GET request with any domain name in the Host header; this is stored and allows for arbitrary domains to be set for certain links displayed to subsequent visitors, potentially an XSS vector.

Timeline

  1. Published
  2. First public exploit (EDB-41885)

Exploit prediction

2.75% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-41885 Concrete5 CMS 8.1.0 - 'Host' Header Injection webapps, 2017-04-14
  • hyp3rlinx.altervista.org http://hyp3rlinx.altervista.org/advisories/CONCRETE5-v8.1.0-HOST-HEADER-INJECTION.txt referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com https://packetstormsecurity.com/files/142145/concrete5-8.1.0-Host-Header-Injection.html referenced PoC, tagged "exploit" by a source, unverified
  • hackerone.com https://hackerone.com/reports/148300 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N
GitHub 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
packagist concrete5/concrete5
<=8.1.0
no fix listed

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Intel 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.