# CVE-2026-14238: Vitepos < 3.6.0 - Admin+ SQL Injection via product-details-report

> Administrators can perform SQL injection via the product-details-report endpoint in the Vitepos WordPress plugin.

- **Severity:** Medium 4.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-q4j7-5cq8-7g9h

## What is CVE-2026-14238?

CVE-2026-14238 is a medium-severity SQL injection vulnerability in Unknown vitepos, published on 10 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The vitepos WordPress plugin before 3.6.0 does not sanitize or parameterize an identifier taken from a REST request body before using it in a database query in one of its report endpoints, allowing users with administrator-level access to perform SQL injection.

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

## Which versions are affected by CVE-2026-14238?


## How do I fix CVE-2026-14238?

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

## Is CVE-2026-14238 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-14238 and fix it if it is affected.

What it is: CVE-2026-14238 is a medium-severity SQL injection vulnerability in Unknown vitepos, published on 10 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-14238 in the wild and no public exploit code.

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

## Sources

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

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