# CVE-2025-28873: WordPress Shuffle plugin <= 0.5 - SQL Injection vulnerability

> An attacker can perform blind SQL injection attacks against the Shuffle WordPress plugin to read sensitive database information.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Mar 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-hph8-p5j3-prh4

## What is CVE-2025-28873?

CVE-2025-28873 is a high-severity SQL injection vulnerability in Scott Taylor Shuffle, published on 26 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Scott Taylor Shuffle shuffle allows Blind SQL Injection.This issue affects Shuffle: from n/a through <= 0.5.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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


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

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

## Is CVE-2025-28873 being exploited?

There is no known exploitation of CVE-2025-28873 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-28873 is a high-severity SQL injection vulnerability in Scott Taylor Shuffle, published on 26 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-28873 in the wild and no public exploit code.

Affected product: Scott Taylor Shuffle. 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-28873/ (Markdown: https://insights.sbomify.com/CVE-2025-28873/index.md)
```

## Sources

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

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