CVE-2022-3999: The DPD Baltic Shipping WordPress plugin before 1.2.57 does not have authorisation and CSRF in an AJAX action,

Q: How do I fix CVE-2022-3999?

woocommerce shipping: upgrade to newer than 1.2.11. Exact commands for each OS are on this page.

Q: Is CVE-2022-3999 being exploited?

CVE-2022-3999 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-3999 affect?

CVE-2022-3999 affects woocommerce shipping. Severity is high (CVSS 8.1). 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 blo

Q: How urgent is CVE-2022-3999?

Priority 43/100. High severity; Public exploit reference

This month

HIGH 8.1UPGRADE

CVE-2022-3999 is a high-severity flaw (CVSS 8.1) affecting woocommerce shipping. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	8.1 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.4% (top 61%)
CISA exploited list	No
Weakness	CWE-352, CWE-862
Published	2022-12-12
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: dpdgroup

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-12-12 18:15 UTCPublished CVE record published
2026-06-17 05:00 UTCUpdated Record last modified

dpdgroup woocommerce shipping UPGRADE

Affected: <= 1.2.11

Fixed in: newer than 1.2.11

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy woocommerce-shipping || rpm -q woocommerce-shipping || woocommerce-shipping --version

2. UPGRADE to newer than 1.2.11 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade woocommerce-shipping

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade woocommerce-shipping

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-3999?

woocommerce shipping: upgrade to newer than 1.2.11. Exact commands for each OS are on this page.

Is CVE-2022-3999 being exploited?

CVE-2022-3999 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-3999 affect?

CVE-2022-3999 affects woocommerce shipping. Severity is high (CVSS 8.1). 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 blo

How urgent is CVE-2022-3999?

Priority 43/100. High severity; Public exploit reference

Software pages

WordPress vulnerabilities · WooCommerce vulnerabilities

Related CVEs

CVE-2022-4000 MEDIUM 4.8 UPGRADE The WooCommerce Shipping WordPress plugin through 1.2.11 does not sanitise and escape some of its settings, wh

References

← Back to latest CVEs