# CVE-2026-67350: Serendipity < 2.6.1 Open Redirect via exit.php

> Unauthenticated attackers can redirect users to malicious sites via a crafted URL in Serendipity when the Track Exits plugin is configured for comment redirection.

- **Severity:** Low 2.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **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:** 31 Jul 2026
- **Updated:** 31 Jul 2026
- **Also known as:** GHSA-77rw-27c5-4hxm, GHSA-xcqg-793j-q344

## What is CVE-2026-67350?

CVE-2026-67350 is a low-severity vulnerability in s9y Serendipity, published on 31 Jul 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

Serendipity before 2.6.1 contains an open redirect vulnerability in exit.php that allows unauthenticated attackers to redirect users to arbitrary external sites by supplying a malicious Base64-encoded url parameter when the Track Exits plugin is configured with commentredirection set to s9y. Attackers can craft trusted-looking URLs leveraging the legitimate blog domain to conduct phishing, deliver malware, or bypass URL reputation filters.

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

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


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

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

## Is CVE-2026-67350 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67350 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-67350 is a low-severity vulnerability in s9y Serendipity, published on 31 Jul 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67350 exists.

Affected product: s9y Serendipity. 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-67350/ (Markdown: https://insights.sbomify.com/CVE-2026-67350/index.md)
```

## Sources

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

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