CVE-2025-14440
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 · uneditedThe JAY Login & Register plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 2.4.01. This is due to incorrect authentication checking in the 'jay_login_register_process_switch_back' function with the 'jay_login_register_process_switch_back' cookie value. This makes it possible for unauthenticated attackers to log in as any existing user on the site, such as an administrator, if they have access to the user id.
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 confidenceThe JAY Login & Register WordPress plugin up to version 2.4.01 contains an authentication bypass vulnerability in the 'jay_login_register_process_switch_back' function. The function incorrectly validates authentication by trusting the 'jay_login_register_process_switch_back' cookie value without proper verification, allowing unauthenticated attackers to log in as any user by providing that user's ID.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- 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 plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for the 'jay-login-register' folder, or view installed plugins in the WordPress admin dashboard under Plugins > Installed PluginsAffected if The JAY Login & Register plugin is present and active
-
Determine installed plugin versionAccess the plugin files and locate the main PHP file (usually jay-login-register.php) and check the 'Version' header in the plugin comment block, or view the version in the WordPress admin plugin listAffected if The installed version is 2.4.01 or lower (versions up to 2.4.01 are affected; version 2.4.02 and later are fixed)
-
Check for vulnerable function exposureInspect the plugin source code for the 'jay_login_register_process_switch_back' function and verify it handles the 'jay_login_register_process_switch_back' cookie without proper user authentication validationAffected if The function exists and processes the cookie without validating the user's identity through proper authentication mechanisms
You are affected if the JAY Login & Register plugin is installed with version 2.4.01 or earlier and the vulnerable switch_back function is present and accessible.
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 the JAY Login & Register plugin to version 2.4.02 or later. If immediate update is not possible, consider disabling the plugin or implementing additional authentication controls at the web application firewall level.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14440 — 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-2025-14440 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