# CVE-2017-7725: Concrete CMS vulnerable to cross-site scripting (XSS)

> Attackers can inject malicious scripts via Host header poisoning in concrete5 when canonical URL is unset, leading to XSS for visitors.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-2mvg-c6mg-3q63

## What is CVE-2017-7725?

CVE-2017-7725 is a medium-severity cross-site scripting vulnerability in Concretecms Concrete Cms, published on 13 Apr 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2017-7725?

2 open source packages ship an affected version, including concrete5/concrete5. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `concrete5/concrete5` | Packagist | All versions to 8.1.0 | None |
| `concrete5/concrete5` | Packagist | All versions to 8.1.0 | None |

Products: Concretecms Concrete Cms.

## How do I fix CVE-2017-7725?

No fix has been published for CVE-2017-7725 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-7725 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-7725 exists.

Public exploit code:

- Concrete5 CMS 8.1.0 - 'Host' Header Injection (exploitdb)

## Other vulnerabilities in Concretecms Concrete Cms

- [CVE-2023-48648](https://insights.sbomify.com/CVE-2023-48648/): Concrete CMS allows unauthorized access because directories can be created with insecure permissions (critical 9.8)
- [CVE-2022-21829](https://insights.sbomify.com/CVE-2022-21829/): Code injection in concrete CMS (critical 9.8)
- [CVE-2021-22958](https://insights.sbomify.com/CVE-2021-22958/): Server-Side Request Forgery vulnerability in concrete5 (critical 9.8)
- [CVE-2021-40098](https://insights.sbomify.com/CVE-2021-40098/): Path traversal in n/a (critical 9.8)
- [CVE-2026-8134](https://insights.sbomify.com/CVE-2026-8134/): Concrete CMS Vulnerable to Relative Path Traversal (critical 9.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-7725 and fix it if it is affected.

What it is: CVE-2017-7725 is a medium-severity cross-site scripting vulnerability in Concretecms Concrete Cms, published on 13 Apr 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-7725 exists.

Affected packages and fixed versions:
- concrete5/concrete5 (Packagist): affected all versions up to 8.1.0; no fix listed
- concrete5/concrete5 (Packagist): affected all versions up to 8.1.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-7725/ (Markdown: https://insights.sbomify.com/CVE-2017-7725/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-7725
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-7725
- OSV: https://osv.dev/vulnerability/CVE-2017-7725

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-7725/
Summaries are generated and may contain mistakes; the official description above is the record.