dbcve.org
Redirect 404 Error Page To Homepage Or Custom Page With LogsWordPress extension · Wpvibes

CVE-2023-47530

HIGH · 7.2 CVSS v3.1 Published 2023-12-18
Fix available
A fix is available. Upgrade to 1.8.8 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in WPVibes Redirect 404 Error Page to Homepage or Custom Page with Logs allows SQL Injection.This issue affects Redirect 404 Error Page to Homepage or Custom Page with Logs: from n/a through 1.8.7.

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 confidence

SQL injection vulnerability in WPVibes Redirect 404 Error Page plugin allows attackers to inject malicious SQL commands through unsanitized user input processed by the plugin, potentially enabling unauthorized database access, data exfiltration, or manipulation.

MitigationUpdate the plugin to the latest version beyond 1.8.7 which should contain the patched code. Until then, disable the plugin if possible or implement Web Application Firewall rules to block suspicious SQL patterns in requests.

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
Redirect 404 Error Page To Homepage Or Custom Page With LogsWordPress extension
Affected:< 1.8.8

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the WPVibes Redirect 404 plugin
    Access your WordPress site via FTP or file manager and navigate to /wp-content/plugins/ directory. Look for a folder named 'redirect-404-error-page' or similar WPVibes plugin folder.
    Affected if The plugin folder exists in the plugins directory.
  2. Identify the installed version
    In the WordPress admin dashboard, go to Plugins > Installed Plugins. Find 'WPvibes Redirect 404 Error Page To Homepage Or Custom Page With Logs' and read the version number displayed beneath the plugin name.
    Affected if The version number shown is less than 1.8.8.
  3. Verify plugin activation status
    In the WordPress admin under Plugins > Installed Plugins, check whether the WPVibes Redirect 404 plugin is currently active (the plugin toggle is enabled).
    Affected if The plugin is active and the version is below 1.8.8.
  4. Inspect plugin source for SQL handling
    Using a file editor, open the main plugin PHP file (usually redirect-404-error-page.php or similar in the plugin folder) and search for SQL query functions like $wpdb->prepare, mysql_query, or direct variable interpolation in SQL strings.
    Affected if The code contains unsanitized SQL queries using $_GET, $_POST, or $_REQUEST variables directly in SQL statements without using $wpdb->prepare or esc_sql.

You are affected if the WPVibes Redirect 404 Error Page plugin is installed, active, and running version 1.8.7 or lower.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 1.8.8 or later
Fixed in 1.8.8
Interim mitigation

Update the plugin to the latest version beyond 1.8.7 which should contain the patched code. Until then, disable the plugin if possible or implement Web Application Firewall rules to block suspicious SQL patterns in requests.

Recommended fix Moderate confidence

1.8.8

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Redirect 404 Error Page to Homepage or Custom Page with Logs' by WPVibes
  4. If not already updated, click 'Update Now' to upgrade to version 1.8.8
  5. Verify the update completed successfully and the plugin shows version 1.8.8

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Redirect 404 Error Page To Homepage Or Custom Page With Logs Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-47530 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-47530 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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