# CVE-2024-1247: Concrete CMS version 9 before 9.2.5 vulnerable to stored XSS via the Role Name field

> A rogue administrator can inject malicious scripts into the Role Name field, leading to stored XSS execution for other users.

- **Severity:** Low 2.0 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:L/A: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:** 9 Feb 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-q25h-jch8-gfrp

## What is CVE-2024-1247?

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

### Official description

Concrete CMS version 9 before 9.2.5 is vulnerable to  stored XSS via the Role Name field since there is insufficient validation of administrator provided data for that field. A rogue administrator could inject malicious code into the Role Name field which might be executed when users visit the affected page. The Concrete CMS Security team scored this 2 with CVSS v3 vector  AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:L/A:N https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator . Concrete versions below 9 do not include group types so they are not affected by this vulnerability.

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

## Which versions are affected by CVE-2024-1247?

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.2.5 |
| `concrete5/concrete5` | Packagist | From 9.0.0RC1 | 9.2.5 |

Products: Concretecms Concrete Cms.

## How do I fix CVE-2024-1247?

Upgrade concrete5/concrete5 to 9.2.5 or later.

## Is CVE-2024-1247 being exploited?

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

Public exploit code:

- Post Saint <= 1.3.1 plugin for WordPress Arbitrary File Upload  (github_poc): https://github.com/Nxploited/CVE-2024-1247-PoC

## 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-2024-1247 and fix it if it is affected.

What it is: CVE-2024-1247 is a low-severity cross-site scripting vulnerability in Concretecms Concrete Cms, published on 9 Feb 2024. 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-2024-1247 in the wild and no public exploit code.

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

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

## Sources

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

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