WordPress security changelog
MEDIUM CVE-2021-4338 Modified

404 to 301: A security weakness

404 to 301 is affected by a security weakness. Exploitation requires an authenticated WordPress account. The resulting impact depends on how the affected component exposes the vulnerable operation.

CVE / CNA score 6.4 CVSS 3.1 · security@wordfence.com
NVD score 5.4 CVSS 3.1 · nvd@nist.gov
Component
404 to 301
Plugin slug
404-to-301
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Jun 07, 2023
Weakness
CWE-284 — Improper Access Control
CWE-862 — Missing Authorization

This CVE was published Jun 07, 2023 and is one of 3 known issues for this plugin.

What to do

Update, patch or deactivate.

Update 404 to 301 to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

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.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

NVD vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

References

Primary and upstream sources