dbcve.org
Woocommerce Login RedirectApplication · Wpdoctor

CVE-2023-48773

HIGH · 8.8 CVSS v3.1 Published 2023-12-18
Fix available
A fix is available. Upgrade to after 2.2.4 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Cross-Site Request Forgery (CSRF) vulnerability in WP Doctor WooCommerce Login Redirect.This issue affects WooCommerce Login Redirect: from n/a through 2.2.4.

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

Cross-Site Request Forgery (CSRF) vulnerability in the WooCommerce Login Redirect plugin allows attackers to trick authenticated administrators or users into performing unintended login redirect configuration changes. The lack of proper CSRF tokens in the plugin's admin actions enables malicious requests to be forged from other sites.

MitigationUpdate the WooCommerce Login Redirect plugin to the latest version beyond 2.2.4 if available, or implement anti-CSRF tokens (nonce validation) in the plugin's form submissions and admin actions.

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
Woocommerce Login RedirectApplication
Affected:<= 2.2.4

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Verify plugin installation and version
    Check the installed version of the Wpdoctor WooCommerce Login Redirect plugin in WordPress under Plugins > Installed Plugins, or inspect the plugin's main PHP file header for the 'Version' field. Compare against the affected range: <= 2.2.4.
    Affected if The installed version is 2.2.4 or lower.
  2. Confirm admin access capability
    Verify that you have administrator-level access to the WordPress site and can access the WooCommerce Login Redirect plugin settings page under WooCommerce > Login Redirect.
    Affected if You have admin access and the plugin settings are reachable.
  3. Inspect admin action handlers for nonce validation
    Examine the main plugin PHP file for admin action handlers (functions that handle POST/GET requests like 'update_option', 'save_settings', or similar). Look for the presence of 'wp_verify_nonce' or 'check_admin_referer' calls before processing any configuration changes.
    Affected if Admin action functions exist but contain no nonce verification code (wp_verify_nonce, check_admin_referer, or wp_nonce_field are absent).
  4. Check form submissions for CSRF tokens
    If the plugin has settings forms, view the HTML source of the plugin settings page in the admin panel. Look for hidden nonce fields (typically named '_wpnonce' or similar) in the form markup.
    Affected if Settings forms render without any hidden nonce input fields.

You are affected if the Wpdoctor WooCommerce Login Redirect plugin version is 2.2.4 or lower and admin action handlers lack nonce verification logic.

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 2.2.4
Interim mitigation

Update the WooCommerce Login Redirect plugin to the latest version beyond 2.2.4 if available, or implement anti-CSRF tokens (nonce validation) in the plugin's form submissions and admin actions.

Recommended fix Moderate confidence

Latest version of WooCommerce Login Redirect (check wordpress.org for current stable release)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the WooCommerce Login Redirect plugin
  4. 4. Check if an update is available and update to the latest version
  5. 5. Alternatively, manually download the latest version from wordpress.org or the vendor and upload via Plugins > Add New > Upload Plugin
  6. 6. Verify the update was successful and test login redirect functionality

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

Fix this in Woocommerce Login Redirect Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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