# CVE-2022-28923: Open Redirect in Caddy

> Attackers can redirect users to phishing sites via crafted URLs in Caddy, requiring an upgrade to mitigate.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A: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:** Yes
- **Published:** 6 Feb 2023
- **Updated:** 26 Mar 2025
- **Also known as:** DEBIAN-CVE-2022-28923, GHSA-qpm3-vr34-h8w8, GO-2023-1567

## What is CVE-2022-28923?

CVE-2022-28923 is a medium-severity vulnerability in n/a, published on 6 Feb 2023. 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

Caddy v2.4.6 was discovered to contain an open redirection vulnerability which allows attackers to redirect users to phishing websites via crafted URLs.

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

## Which versions are affected by CVE-2022-28923?

3 open source packages ship an affected version, including github.com/caddyserver/caddy/v2. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/caddyserver/caddy/v2` | Go | All versions | 2.5.0-beta.1 |
| `github.com/caddyserver/caddy/v2` | Go | All versions | 2.5.0-beta.1 |
| `github.com/caddyserver/caddy/v2` | Go | All versions | 2.5.0-beta.1 |

Products: Caddyserver Caddy.

## How do I fix CVE-2022-28923?

Upgrade github.com/caddyserver/caddy/v2 to 2.5.0-beta.1 or later.

## Is CVE-2022-28923 being exploited?

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

Public exploit code:

- Caddy 2.4.6 - Open Redirect (nuclei): http/cves/2022/CVE-2022-28923.yaml

## Other vulnerabilities in n/a

- [CVE-2018-21246](https://insights.sbomify.com/CVE-2018-21246/): Caddy vulnerable to Authentication Bypass due to mishandling of TLS client authentication (critical 9.8)
- [CVE-2026-27590](https://insights.sbomify.com/CVE-2026-27590/): Caddy: Unicode case-folding length expansion causes incorrect split_path index in FastCGI transport (high 8.9)
- [CVE-2026-27586](https://insights.sbomify.com/CVE-2026-27586/): Caddy's mTLS client authentication silently fails open when CA certificate file is missing or malformed (high 8.8)
- [CVE-2026-45135](https://insights.sbomify.com/CVE-2026-45135/): Caddy: Unsafe Unicode Handling in FastCGI splitPos Allows Execution of Non-PHP Files (high 8.1)
- [CVE-2026-52845](https://insights.sbomify.com/CVE-2026-52845/): Caddy: FastCGI header normalization bypass in `forward_auth copy_headers` (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-28923 and fix it if it is affected.

What it is: CVE-2022-28923 is a medium-severity vulnerability in n/a, published on 6 Feb 2023. 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-2022-28923 exists.

Affected packages and fixed versions:
- github.com/caddyserver/caddy/v2 (Go): affected all versions; fixed in 2.5.0-beta.1
- github.com/caddyserver/caddy/v2 (Go): affected all versions; fixed in 2.5.0-beta.1
- github.com/caddyserver/caddy/v2 (Go): affected all versions; fixed in 2.5.0-beta.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-2022-28923/ (Markdown: https://insights.sbomify.com/CVE-2022-28923/index.md)
```

## Sources

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

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