# CVE-2025-13417: Plugin Organizer < 10.2.4 - Subscriber+ SQLi

> Subscribers can execute SQL injection attacks in the Plugin Organizer WordPress plugin due to unsanitized parameters, potentially compromising database integrity.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Dec 2025
- **Updated:** 29 Dec 2025
- **Also known as:** GHSA-74hv-hc8x-rcwg

## What is CVE-2025-13417?

CVE-2025-13417 is a high-severity SQL injection vulnerability in Unknown Plugin Organizer, published on 29 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Plugin Organizer WordPress plugin before 10.2.4 does not sanitize and escape a parameter before using it in a SQL statement, allowing subscribers to perform SQL injection attacks.

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


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

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

## Is CVE-2025-13417 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13417 is a high-severity SQL injection vulnerability in Unknown Plugin Organizer, published on 29 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-13417 exists.

Affected product: Unknown Plugin Organizer. 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-13417/ (Markdown: https://insights.sbomify.com/CVE-2025-13417/index.md)
```

## Sources

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

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