# CVE-2026-8082: Bpost Shipping Platform < 3.2.3 - Unauthenticated SQL Injection

> Unauthenticated attackers can perform time-based blind SQL injection via unsanitized parameters during WooCommerce order submission in the bpost shipping plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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:** 21 Jul 2026
- **Updated:** 21 Jul 2026
- **Also known as:** GHSA-3gcj-q53g-wp8x

## What is CVE-2026-8082?

CVE-2026-8082 is a high-severity SQL injection vulnerability in Unknown bpost-shipping-platform, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The bpost-shipping-platform WordPress plugin before 3.2.3 does not properly sanitize a parameter before using it in a SQL query during WooCommerce order submission, allowing unauthenticated attackers to perform time-based blind SQL injection on stores running this bpost-shipping-platform WordPress plugin before 3.2.3.

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

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


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

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

## Is CVE-2026-8082 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-8082 is a high-severity SQL injection vulnerability in Unknown bpost-shipping-platform, published on 21 Jul 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-2026-8082 exists.

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

## Sources

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

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