301 RedirectsWordPress extension · Webfactoryltd
CVE-2021-24142
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUnvaludated input in the 301 Redirects - Easy Redirect Manager WordPress plugin, versions before 2.51, did not sanitise its "Redirect From" column when importing a CSV file, allowing high privilege users to perform SQL injections.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe 301 Redirects - Easy Redirect Manager WordPress plugin versions before 2.51 failed to properly sanitise the 'Redirect From' column when importing CSV files, allowing authenticated high-privilege users to inject malicious SQL queries through the import functionality.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
301 RedirectsWordPress extension
< 2.51CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if the 301 Redirects plugin is installedCheck the WordPress plugins directory for the '301-redirects' or 'wf-301-redirects' plugin folder, or query the wp_options table for the active_plugins entry containing '301-redirects'Affected if The plugin is present and active in the WordPress installation
-
Determine the installed plugin versionRead the plugin header from the main plugin PHP file (typically in wp-content/plugins/301-redirects/ or similar) to extract the Version field, or query the wp_options table for the option_name containing the plugin versionAffected if The version number is less than 2.51 or cannot be determined (assumed vulnerable)
-
Verify if CSV import functionality is accessibleCheck if the user has access to the plugin's import feature by reviewing WordPress user capabilities for 'import' or 'manage_options' roles, or examine if the plugin admin menu includes import optionsAffected if Authenticated users with high privileges (administrator) can access or have recently used the CSV import feature
-
Review recent plugin activity logsCheck WordPress debug logs, server access logs, or any plugin-specific logs for CSV import operations on the 'Redirect From' field, particularly around the time of the CVE disclosure (early 2021)Affected if CSV import actions on redirect rules are present in logs or the database
A user is affected if the 301 Redirects - Easy Redirect Manager plugin version is below 2.51 AND high-privilege authenticated users have access to or have used the CSV import functionality.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data2.51
Update the 301 Redirects - Easy Redirect Manager plugin to version 2.51 or later to obtain the fixed code with proper input sanitisation. If immediate update is not possible, disable the CSV import feature until the patch can be applied.
Fix this in 301 Redirects
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-24142 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-24142 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data