# CVE-2026-16981: DHL for WooCommerce < 4.0.1 - Unauthenticated Shipping Label Download via IDOR

> Unauthenticated attackers can download all shipping labels containing customer PII due to missing authorization checks in the DHL for WooCommerce plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 Aug 2026
- **Updated:** 6 Aug 2026
- **Also known as:** GHSA-xqqx-fcgc-wmxp

## What is CVE-2026-16981?

CVE-2026-16981 is a medium-severity missing authorization vulnerability in Unknown DHL Shipping Germany for WooCommerce, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The DHL Shipping Germany for WooCommerce WordPress plugin before 4.0.1 does not perform any authorization check (no capability, nonce, login, or ownership check) on one of its shipping-label download endpoints, so an unauthenticated attacker can enumerate sequential ids and download every stored shipping label, each containing the customer's full name, complete postal address, and order reference.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-16981 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16981 is a medium-severity missing authorization vulnerability in Unknown DHL Shipping Germany for WooCommerce, published on 5 Aug 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-16981 in the wild and no public exploit code.

Affected product: Unknown DHL Shipping Germany for WooCommerce. 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-16981/ (Markdown: https://insights.sbomify.com/CVE-2026-16981/index.md)
```

## Sources

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

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