# CVE-2023-3771: T1 theme <= 19.0 - Open Redirect

> An unauthenticated attacker can redirect users to arbitrary websites via the T1 WordPress theme, potentially facilitating phishing attacks.

- **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:** No
- **Published:** 16 Jan 2024
- **Updated:** 20 Jun 2025
- **Also known as:** GHSA-9mw7-8x3h-gcqc

## What is CVE-2023-3771?

CVE-2023-3771 is a medium-severity vulnerability in Unknown t1, published on 16 Jan 2024. 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

The T1 WordPress theme through 19.0 is vulnerable to unauthenticated open redirect with which any attacker and redirect users to arbitrary websites.

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

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

It affects 1 product.


Products: T1 Project T1.

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

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

## Is CVE-2023-3771 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-3771 and fix it if it is affected.

What it is: CVE-2023-3771 is a medium-severity vulnerability in Unknown t1, published on 16 Jan 2024. 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-2023-3771 exists.

Affected product: Unknown t1. 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-2023-3771/ (Markdown: https://insights.sbomify.com/CVE-2023-3771/index.md)
```

## Sources

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

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