# CVE-2025-22799: WordPress Neon Product Designer Plugin <= 2.2.0 - SQL Injection vulnerability

> Attackers can execute arbitrary SQL commands via the Neon Product Designer plugin, potentially reading or modifying database contents.

- **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:** 15 Jan 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-9mjh-4fxm-m933

## What is CVE-2025-22799?

CVE-2025-22799 is a high-severity SQL injection vulnerability in vertim Neon Product Designer, published on 15 Jan 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 vertim Neon Product Designer neon-product-designer-for-woocommerce allows SQL Injection.This issue affects Neon Product Designer: from n/a through <= 2.2.0.

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

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


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

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

## Is CVE-2025-22799 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-22799 is a high-severity SQL injection vulnerability in vertim Neon Product Designer, published on 15 Jan 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-22799 in the wild and no public exploit code.

Affected product: vertim Neon Product Designer. 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-22799/ (Markdown: https://insights.sbomify.com/CVE-2025-22799/index.md)
```

## Sources

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

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