CVE-2021-4338

404 to 301 <= 3.0.7 - Missing Authorization to Redirect Creation

2021-06-18 00:00
Jerome Bruandet

Strategic Overview

Status
Patched in 3.0.8
Affected Plugin
404 to 301 – Redirect Manager, 301 Redirection, 404 Error Logs & 404 Monitoring
Affected Version
<= 3.0.7
CVSS
6.4Medium
Weakness type
CWE-284 · Improper Access Control
CVE
CVE-2021-4338
View all 404 to 301 – Redirect Manager, 301 Redirection, 404 Error Logs & 404 Monitoring vulnerabilities

At a glance

CVE-2021-4338 is a medium-severity Improper Access Control vulnerability in the 404 to 301 WordPress plugin, affecting versions <= 3.0.7. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 3.0.8; sites on affected versions should update now. Disclosed June 2021, reported by Jerome Bruandet.

Vulnerability Overview

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.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-284: Improper Access Control

Reaching this weakness in 404 to 301 <= 3.0.7 takes a caller who can reach the endpoint. Improper access control means the code decides what a caller may do using something other than their actual permissions, so the decision can be wrong without any check appearing to be missing.

Whoever can shape the request decides the answer, so the protected action runs for callers the code never meant to allow. For 404 to 301 the fix is 3.0.8: builds <= 3.0.7 are affected, anything from 3.0.8 onward is not.

Remediation

Update to version 3.0.8, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: 404 to 301 3.0.8 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2021-4338https://www.wordfence.com/threat-intel/vulnerabilities/id/05d6b27f-b1e5-4bb8-b7db-f8295a5e0d5bhttps://nvd.nist.gov/vuln/detail/CVE-2021-4338

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C