CVE-2024-50478
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 · uneditedAuthentication Bypass by Primary Weakness vulnerability in Swoop 1-Click Login: Passwordless Authentication allows Authentication Bypass.This issue affects 1-Click Login: Passwordless Authentication: 1.4.5.
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 confidenceThis is an authentication bypass vulnerability in the Swoop 1-Click Login passwordless authentication plugin for WordPress, affecting version 1.4.5. The vulnerability allows attackers to bypass the authentication mechanism and gain unauthorized access without valid credentials, exploiting a primary weakness in the authentication flow.
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= _passwordless_authenticationCVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Verify Swoop 1-Click Login plugin is installedCheck your CMS plugin directory or admin panel for the 'Swoopnow 1 Click Login' or 'Swoop 1-Click Login' plugin. In WordPress, navigate to Plugins > Installed Plugins and look for this plugin.Affected if The plugin appears in your installed plugins list
-
Identify the installed plugin versionIn the plugin admin panel, click on the plugin to view its details, or inspect the plugin header in the main plugin file (usually found in wp-content/plugins/swoop-1-click-login or similar path) where the Version: tag is defined.Affected if The version is 1.4.5 exactly, or falls within the affected version range for this vulnerability
-
Confirm passwordless authentication is enabledNavigate to the plugin settings in your CMS admin panel. Look for authentication settings related to '1-Click Login', 'Passwordless Login', or 'Swoop Authentication' and verify if the feature is turned on/enabled.Affected if Passwordless authentication mode is active or configured in the plugin settings
-
Check for any custom authentication rules or IP whitelistsReview the plugin configuration for any authentication bypass rules, IP whitelisting settings, or API key configurations that may indicate exposure to the bypass vulnerability.Affected if Authentication bypass rules or overly permissive settings are configured
You are affected if the Swoop 1-Click Login plugin version 1.4.5 is installed AND passwordless authentication is enabled in your environment.
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 dataUpgrade to a patched version of Swoop 1-Click Login immediately, as the 9.8 CVSS score indicates a critical, easily exploitable flaw that grants unauthorized access.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50478 — 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-2024-50478 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