Login And Logout RedirectWordPress extension · Swapnilpatil
CVE-2023-41648
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 · uneditedURL Redirection to Untrusted Site ('Open Redirect') vulnerability in Swapnil V. Patil Login and Logout Redirect.This issue affects Login and Logout Redirect: from n/a through 2.0.3.
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 · moderate confidenceOpen redirect vulnerability in the Login and Logout Redirect WordPress plugin allows attackers to craft malicious URLs containing untrusted redirect destinations that can redirect authenticated users to external malicious sites, potentially facilitating phishing attacks.
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
Login And Logout RedirectWordPress extension
<= 2.0.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin installationIn WordPress admin, navigate to Plugins > Installed Plugins and search for 'Swapnilpatil Login And Logout Redirect' or 'Login And Logout Redirect'. Alternatively, check the /wp-content/plugins/ directory for a folder containing 'login-and-logout-redirect' in the filename.Affected if The plugin is present in the WordPress installation
-
Identify installed versionIn the WordPress plugins list, locate the plugin and note the version number displayed beneath the plugin name. If not visible in the admin interface, open the main plugin PHP file (often named login-and-logout-redirect.php) and inspect the 'Version' header in the plugin comment block at the top of the file.Affected if Version number is 2.0.3 or lower
-
Verify plugin is activeIn WordPress admin > Plugins, check that the plugin shows as 'Active' rather than 'Inactive' or 'Must Use'. An inactive plugin with the vulnerability present would not be exploitable.Affected if Plugin is currently activated on the site
-
Confirm redirect settings are configuredAccess the plugin settings page in WordPress admin (typically under Settings > Login Logout Redirect or similar) and verify if any login or logout redirect URLs are configured. The vulnerability affects sites where redirect functionality is enabled.Affected if Redirect URLs are set in the plugin configuration
Your environment is affected if the Swapnilpatil Login And Logout Redirect plugin version 2.0.3 or lower is installed, active, and has redirect functionality configured.
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 dataUpdate to the latest patched version of the Login and Logout Redirect plugin; if no patch is available, replace with a secure alternative authentication redirect plugin or remove the plugin entirely.
Fix this in Login And Logout Redirect
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41648 — 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-2023-41648 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