# CVE-2025-68509: WordPress User Submitted Posts plugin <= 20251121 - Open Redirection vulnerability

> Attackers can redirect users to malicious sites via phishing, requiring WordPress plugin users to update immediately.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/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:** 24 Dec 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-3wm8-ph73-r7q9

## What is CVE-2025-68509?

CVE-2025-68509 is a medium-severity vulnerability in Jeff Starr User Submitted Posts, published on 24 Dec 2025. 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

URL Redirection to Untrusted Site ('Open Redirect') vulnerability in Jeff Starr User Submitted Posts user-submitted-posts allows Phishing.This issue affects User Submitted Posts: from n/a through <= 20251121.

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

## Which versions are affected by CVE-2025-68509?


## How do I fix CVE-2025-68509?

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

## Is CVE-2025-68509 being exploited?

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

Public exploit code:

- User Submitted Posts <= 20251121 - Unauthenticated Open Redirect (nuclei): http/cves/2025/CVE-2025-68509.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68509 and fix it if it is affected.

What it is: CVE-2025-68509 is a medium-severity vulnerability in Jeff Starr User Submitted Posts, published on 24 Dec 2025. 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-2025-68509 exists.

Affected product: Jeff Starr User Submitted Posts. 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-2025-68509/ (Markdown: https://insights.sbomify.com/CVE-2025-68509/index.md)
```

## Sources

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

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