# CVE-2026-109160: PublicCMS pay Endpoint SafeConfigComponent.java SafeConfigComponent.getSafeUrl redirect

> Attackers can exploit an open redirect in the PublicCMS pay endpoint via the returnUrl parameter to redirect users to malicious sites.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **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 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-8c56-665g-jg6c

## What is CVE-2026-109160?

CVE-2026-109160 is a medium-severity vulnerability in PublicCMS, published on 13 Oct 2026. 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

A vulnerability was determined in PublicCMS up to 5.202608.a. Affected by this issue is the function SafeConfigComponent.getSafeUrl of the file publiccms-core/src/main/java/com/publiccms/logic/component/config/SafeConfigComponent.java of the component pay Endpoint. Executing a manipulation of the argument returnUrl can lead to open redirect. It is possible to launch the attack remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2026-109160?


## How do I fix CVE-2026-109160?

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

## Is CVE-2026-109160 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-109160 and fix it if it is affected.

What it is: CVE-2026-109160 is a medium-severity vulnerability in PublicCMS, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-109160 in the wild and no public exploit code.

Affected product: PublicCMS. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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