# CVE-2025-14124: Team < 5.0.11 - Unauthenticated SQLi

> Unauthenticated attackers can execute arbitrary SQL commands via an AJAX action in the Team WordPress plugin, potentially accessing or modifying database content.

- **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:** 5 Jan 2026
- **Updated:** 5 Jan 2026
- **Also known as:** GHSA-jwg6-9jwg-258q

## What is CVE-2025-14124?

CVE-2025-14124 is a high-severity SQL injection vulnerability in Unknown Team, published on 5 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Team  WordPress plugin before 5.0.11 does not properly sanitize and escape a parameter before using it in a SQL statement via an AJAX action available to unauthenticated users, leading to a SQL injection.

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


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

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

## Is CVE-2025-14124 being exploited?

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

Public exploit code:

- Unauthenticated SQL Injection (Time-Based Blind) (github_poc): https://github.com/hyunchiya/CVE-2025-14124
- Team WordPress Plugin (TLP Team) <= 5.0.9 - SQL Injection (nuclei): http/cves/2025/CVE-2025-14124.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14124 is a high-severity SQL injection vulnerability in Unknown Team, published on 5 Jan 2026. 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-14124 exists.

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

## Sources

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

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