# CVE-2025-8573: Concrete CMS 9 through 9.4.2 is vulnerable to Stored XSS from Home Folder on Members Dashboard page

> A rogue admin can inject malicious scripts via the Home Folder setting, leading to stored XSS attacks against users on the Members Dashboard.

- **Severity:** Low 2.0 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 5 Aug 2025
- **Updated:** 11 Aug 2025
- **Also known as:** GHSA-c5xf-rmv4-j85h

## What is CVE-2025-8573?

CVE-2025-8573 is a low-severity cross-site scripting vulnerability in Concretecms Concrete Cms, published on 5 Aug 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Concrete CMS versions 9 through 9.4.2 are vulnerable to Stored XSS from Home Folder on Members Dashboard page.  Version 8 was not affected. A rogue admin could set up a malicious folder containing XSS to which users could be directed upon login. The Concrete CMS security team gave this vulnerability a CVSS v.4.0 score of 2.0 with vector CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N. Thanks sealldev  (Noah Cooper) for reporting via HackerOne.

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

## Which versions are affected by CVE-2025-8573?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `concrete5/concrete5` | Packagist | From 9.0.0RC1 | 9.4.3 |
| `concrete5/concrete5` | Packagist | From 9.0.0RC1 | 9.4.3 |

Products: Concretecms Concrete Cms.

## How do I fix CVE-2025-8573?

Upgrade concrete5/concrete5 to 9.4.3 or later.

## Is CVE-2025-8573 being exploited?

There is no known exploitation of CVE-2025-8573 in the wild and no public exploit code.

Public exploit code:

- Concrete CMS 9.4.3 - Stored XSS (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-2025-8573 and fix it if it is affected.

What it is: CVE-2025-8573 is a low-severity cross-site scripting vulnerability in Concretecms Concrete Cms, published on 5 Aug 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-8573 in the wild and no public exploit code.

Affected packages and fixed versions:
- concrete5/concrete5 (Packagist): affected from 9.0.0RC1; fixed in 9.4.3
- concrete5/concrete5 (Packagist): affected from 9.0.0RC1; fixed in 9.4.3

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-2025-8573/ (Markdown: https://insights.sbomify.com/CVE-2025-8573/index.md)
```

## Sources

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

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