# CVE-2022-3999: WooCommerce Shipping - DPD baltic < 1.2.57 - Subscriber+ Arbitrary Options Deletion

> Authenticated users can delete arbitrary blog options due to missing authorization and CSRF checks, potentially making the site unavailable.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **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:** 12 Dec 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-7rm4-78m3-r89p

## What is CVE-2022-3999?

CVE-2022-3999 is a high-severity missing authorization vulnerability in Unknown DPD Baltic Shipping, published on 12 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The DPD Baltic Shipping WordPress plugin before 1.2.57 does not have authorisation and CSRF in an AJAX action, which could allow any authenticated users, such as subscriber to delete arbitrary options from the blog, which could make the blog unavailable.

Weakness: CWE-862 (Missing Authorization), CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2022-3999?

It affects 1 product.


Products: Dpdgroup Woocommerce Shipping.

## How do I fix CVE-2022-3999?

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

## Is CVE-2022-3999 being exploited?

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

## Other vulnerabilities in Unknown DPD Baltic Shipping

- [CVE-2022-4000](https://insights.sbomify.com/CVE-2022-4000/): WooCommerce Shipping - DPD baltic < 1.2.11 - Admin+ Stored XSS (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-3999 and fix it if it is affected.

What it is: CVE-2022-3999 is a high-severity missing authorization vulnerability in Unknown DPD Baltic Shipping, published on 12 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3999 exists.

Affected product: Unknown DPD Baltic Shipping. 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-2022-3999/ (Markdown: https://insights.sbomify.com/CVE-2022-3999/index.md)
```

## Sources

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

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