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.
Tracking
Sign in to view the affected projects.
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2022-2017 | 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. |
Github GHSA |
GHSA-2mvg-c6mg-3q63 | Concrete CMS vulnerable to cross-site scripting (XSS) |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
No history.
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2024-08-05T16:12:28.269Z
Reserved: 2017-04-12T00:00:00.000Z
Link: CVE-2017-7725
No data.
Status : Deferred
Published: 2017-04-13T17:59:00.700
Modified: 2025-04-20T01:37:25.860
Link: CVE-2017-7725
No data.
OpenCVE Enrichment
No data.
Weaknesses
EUVD
Github GHSA