# CVE-2024-8572: Gouniverse GoLang CMS FrontendHandler.go PageRenderHtmlByAlias cross site scripting


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 8 Sep 2024
- **Updated:** 10 Sep 2024
- **Also known as:** GHSA-pv7h-hg6m-82j8, GO-2024-3125

## What is CVE-2024-8572?

CVE-2024-8572 is a medium-severity vulnerability in Gouniverse GoLang CMS, published on 8 Sep 2024. 

### Official description

A vulnerability was found in Gouniverse GoLang CMS 1.4.0. It has been declared as problematic. This vulnerability affects the function PageRenderHtmlByAlias of the file FrontendHandler.go. The manipulation of the argument alias leads to cross site scripting. The attack can be initiated remotely. Upgrading to version 1.4.1 is able to address this issue. The patch is identified as 3e661cdfb4beeb9fe2ad507cdb8104c0b17d072c. It is recommended to upgrade the affected component.

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

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

3 open source packages ship an affected version, including github.com/gouniverse/cms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/gouniverse/cms` | Go | All versions | 1.4.1 |
| `github.com/gouniverse/cms` | Go | All versions | 1.4.1 |
| `github.com/gouniverse/cms` | Go | All versions | 1.4.1 |

Products: Gouniverse Golang Cms.

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

Upgrade github.com/gouniverse/cms to 1.4.1 or later.

## Is CVE-2024-8572 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-8572 and fix it if it is affected.

What it is: CVE-2024-8572 is a medium-severity vulnerability in Gouniverse GoLang CMS, published on 8 Sep 2024. 
Exploitation: There is no known exploitation of CVE-2024-8572 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/gouniverse/cms (Go): affected all versions; fixed in 1.4.1
- github.com/gouniverse/cms (Go): affected all versions; fixed in 1.4.1
- github.com/gouniverse/cms (Go): affected all versions; fixed in 1.4.1

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

## Sources

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

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