# CVE-2021-24210: PhastPress < 1.111 - Open Redirect

> An attacker can redirect victims to malicious sites via a malformed request in the PhastPress WordPress plugin, 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:** 5 Apr 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-4mcw-w8hg-ph3c

## What is CVE-2021-24210?

CVE-2021-24210 is a medium-severity vulnerability in Unknown PhastPress, published on 5 Apr 2021. 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

There is an open redirect in the PhastPress WordPress plugin before 1.111 that allows an attacker to malform a request to a page with the plugin and then redirect the victim to a malicious page. There is also a support comment from another user one year ago (https://wordpress.org/support/topic/phast-php-used-for-remote-fetch/) that says that the php involved in the request only go to whitelisted pages but it's possible to redirect the victim to any domain.

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

## Which versions are affected by CVE-2021-24210?

It affects 1 product.


Products: Kiboit Phastpress.

## How do I fix CVE-2021-24210?

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

## Is CVE-2021-24210 being exploited?

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

Public exploit code:

- WordPress PhastPress <1.111 - Open Redirect (nuclei): http/cves/2021/CVE-2021-24210.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-24210 and fix it if it is affected.

What it is: CVE-2021-24210 is a medium-severity vulnerability in Unknown PhastPress, published on 5 Apr 2021. 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-2021-24210 exists.

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

## Sources

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

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