# CVE-2026-14962: ELEX WooCommerce Request a Quote < 2.4.1 - Unauthenticated SQLi via variation_id

> Unauthenticated attackers can exploit SQL injection in the ELEX WooCommerce Request a Quote plugin to extract arbitrary data from the database.

- **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:** 9 Sep 2026
- **Updated:** 9 Sep 2026
- **Also known as:** GHSA-c2fx-847w-vg56

## What is CVE-2026-14962?

CVE-2026-14962 is a high-severity SQL injection vulnerability in Unknown ELEX WooCommerce Request a Quote, published on 9 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The ELEX WooCommerce Request a Quote WordPress plugin before 2.4.1 does not properly sanitise and escape a parameter before using it in a SQL query, allowing unauthenticated users to perform SQL injection attacks and extract arbitrary data from the database.

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

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


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

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

## Is CVE-2026-14962 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14962 is a high-severity SQL injection vulnerability in Unknown ELEX WooCommerce Request a Quote, published on 9 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-14962 in the wild and no public exploit code.

Affected product: Unknown ELEX WooCommerce Request a Quote. 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-14962/ (Markdown: https://insights.sbomify.com/CVE-2026-14962/index.md)
```

## Sources

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

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