CVE-2021-4338: The 404 to 301 plugin for WordPress is vulnerable to authorization bypass due to missing capability checks on

Q: How do I fix CVE-2021-4338?

404 to 301: upgrade to newer than 3.0.7. Exact commands for each OS are on this page.

Q: Is CVE-2021-4338 being exploited?

CVE-2021-4338 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-2021-4338 affect?

CVE-2021-4338 affects 404 to 301. Severity is medium (CVSS 6.4). The 404 to 301 plugin for WordPress is vulnerable to authorization bypass due to missing capability checks on the open_redirect & save_redirect functions in versions up to, and including, 3.0.7. This makes it possible for authenticated atta

Q: How urgent is CVE-2021-4338?

Priority 40/100. Public exploit reference

This month

MEDIUM 6.4UPGRADE

CVE-2021-4338 is a medium-severity flaw (CVSS 6.4) affecting 404 to 301. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The 404 to 301 plugin for WordPress is vulnerable to authorization bypass due to missing capability checks on the open_redirect & save_redirect functions in versions up to, and including, 3.0.7. This makes it possible for authenticated attackers to view, create and edit redirections.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	6.4 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.6% (top 50%)
CISA exploited list	No
Weakness	CWE-284, CWE-862
Published	2023-06-07
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: duckdev

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

Am I affected?

Timeline

2023-06-07 02:15 UTCPublished CVE record published
2026-06-17 04:19 UTCUpdated Record last modified

duckdev 404 to 301 UPGRADE

Affected: <= 3.0.7

Fixed in: newer than 3.0.7

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy 404-to-301 || rpm -q 404-to-301 || 404-to-301 --version

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

sudo apt update && sudo apt install --only-upgrade 404-to-301

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade 404-to-301

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-2021-4338?

404 to 301: upgrade to newer than 3.0.7. Exact commands for each OS are on this page.

Is CVE-2021-4338 being exploited?

CVE-2021-4338 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-2021-4338 affect?

CVE-2021-4338 affects 404 to 301. Severity is medium (CVSS 6.4). The 404 to 301 plugin for WordPress is vulnerable to authorization bypass due to missing capability checks on the open_redirect & save_redirect functions in versions up to, and including, 3.0.7. This makes it possible for authenticated atta

How urgent is CVE-2021-4338?

Priority 40/100. Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2021-24766 MEDIUM 6.5 UPGRADE The 404 to 301 – Redirect, Log and Notify 404 Errors WordPress plugin before 3.0.9 does not have CSRF check in

References

← Back to latest CVEs