# CVE-2023-44760: Concrete CMS Cross-site Scripting vulnerability

> An attacker with admin privileges can inject scripts into SEO tracking codes, though the vendor disputes this as an intended feature.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/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:** No
- **Published:** 23 Oct 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-4qv6-37xq-mgq2

## What is CVE-2023-44760?

CVE-2023-44760 is a medium-severity cross-site scripting vulnerability in Concretecms Concrete Cms, published on 23 Oct 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Multiple Cross Site Scripting (XSS) vulnerabilities in Concrete CMS v.9.2.1 allow an attacker to execute arbitrary code via a crafted script to the Header and Footer Tracking Codes of the SEO & Statistics. NOTE: the vendor disputes this because these header/footer changes can only be made by an admin, and allowing an admin to place JavaScript there is an intentional customization feature. Also, the exploitation method claimed by "sromanhu" does not provide any access to a Concrete CMS session, because the Concrete CMS session cookie is configured as HttpOnly.

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

## Which versions are affected by CVE-2023-44760?

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 9.2.1 | None |
| `concrete5/concrete5` | Packagist | All versions to 9.2.1 | None |

Products: Concretecms Concrete Cms.

## How do I fix CVE-2023-44760?

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

## Is CVE-2023-44760 being exploited?

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

Public exploit code:

- Multiple Cross Site Scripting vulnerability in ConcreteCMS v.9.2.1 allows a local attacker to execute arbitrary code via a crafted script to the Header and Footer Tracking Codes of the SEO & Statistics (github_poc): https://github.com/sromanhu/CVE-2023-44760_ConcreteCMS-Stored-XSS---TrackingCodes

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

What it is: CVE-2023-44760 is a medium-severity cross-site scripting vulnerability in Concretecms Concrete Cms, published on 23 Oct 2023. 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-2023-44760 in the wild and no public exploit code.

Affected packages and fixed versions:
- concrete5/concrete5 (Packagist): affected all versions up to 9.2.1; no fix listed
- concrete5/concrete5 (Packagist): affected all versions up to 9.2.1; 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-2023-44760/ (Markdown: https://insights.sbomify.com/CVE-2023-44760/index.md)
```

## Sources

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

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