dbcve.org
All 404 Pages Redirect To HomepageWordPress extension · Geekcodelab

CVE-2024-24889

MEDIUM · 6.1 CVSS v3.1 Published 2024-02-12
Fix available
A fix is available. Upgrade to after 1.9 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Input During Web Page Generation ('Cross-site Scripting') vulnerability in Geek Code Lab All 404 Pages Redirect to Homepage allows Stored XSS.This issue affects All 404 Pages Redirect to Homepage: from n/a through 1.9.

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

A stored cross-site scripting (XSS) vulnerability exists in the Geek Code Lab 'All 404 Pages Redirect to Homepage' WordPress plugin. The plugin fails to properly sanitize and encode user input when handling 404 pages, allowing attackers to inject malicious JavaScript that persists and executes when visitors encounter 404 errors.

MitigationApply proper input sanitization and output encoding using WordPress security functions (such as esc_html(), esc_attr(), or wp_kses()) to all user-controlled data before rendering. Validate the fix with various XSS payloads to confirm the vulnerability is remediated.

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
All 404 Pages Redirect To HomepageWordPress extension
Affected:<= 1.9

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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. Verify plugin installation
    Navigate to WordPress admin dashboard, go to Plugins > Installed Plugins, and search for 'All 404 Pages Redirect to Homepage' or 'Geekcodelab'. Check the version number displayed under the plugin name.
    Affected if The plugin is installed and shows version 1.9 or lower.
  2. Confirm plugin is active
    In the Plugins list, verify the plugin has an 'Active' status indicator, or check the wp_options table in the database for option_name containing 'all_404' or 'geekcodelab_404'.
    Affected if The plugin is installed, active, and running on the site.
  3. Inspect 404 redirect settings
    Access the plugin settings page (usually under Settings > 404 Redirect or similar). Look for input fields that accept URLs, redirect targets, or custom messages related to 404 handling.
    Affected if The plugin has configurable settings for 404 page handling that accept user input.
  4. Test 404 page behavior
    Visit a non-existent page on the site (e.g., /thispagedoesnotexist123). Inspect the page source using browser developer tools (F12) to see if any user-configured values from the plugin settings are reflected without proper encoding.
    Affected if Custom text, URLs, or messages configured in the plugin appear on 404 pages with unescaped characters (e.g., <script> tags visible in source).
  5. Review plugin source code
    If file access is available, open the main plugin file in wp-content/plugins/all-404-pages-redirect-to-homepage/ or similar path. Search for functions handling 404 redirects and check if they use sanitization functions like esc_html(), esc_attr(), or wp_kses().
    Affected if The plugin code contains output functions without proper sanitization when handling 404-related user inputs.

You are affected if the Geekcodelab All 404 Pages Redirect to Homepage plugin is installed at version 1.9 or lower, is active, and its 404 redirect settings reflect user input without encoding.

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 a release after 1.9
Interim mitigation

Apply proper input sanitization and output encoding using WordPress security functions (such as esc_html(), esc_attr(), or wp_kses()) to all user-controlled data before rendering. Validate the fix with various XSS payloads to confirm the vulnerability is remediated.

Recommended fix Moderate confidence

Latest version > 1.9 (check WordPress Plugin Repository for current stable release)

  1. 1. Backup your WordPress site before making any changes
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Find 'All 404 Pages Redirect to Homepage' by Geek Code Lab
  5. 5. If an update is available, click 'Update Now' to install the latest version
  6. 6. Alternatively, download the latest version from the WordPress Plugin Repository or Geek Code Lab
  7. 7. Verify the update was successful by checking the plugin version
  8. 8. Test that the 404 redirect functionality works correctly after the update
Caveat Review plugin settings after upgrade as configuration changes may occur in major version updates

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

Fix this in All 404 Pages Redirect To Homepage Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-24889 — 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-2024-24889 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