CVE-2025-3746
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 OTP-less one tap Sign in plugin for WordPress is vulnerable to privilege escalation via account takeover in versions 2.0.14 to 2.0.59. This is due to the plugin not properly validating a user's identity prior to updating their details, like email. This makes it possible for unauthenticated attackers to change arbitrary users' email addresses, including administrators, and leverage that to reset the user's password and gain access to their account. Additionally, the plugin returns authentication cookies in the response, which can be used to access the account directly.
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 OTP-less one tap Sign in plugin for WordPress fails to validate user identity before allowing email address updates, enabling unauthenticated attackers to modify any user's email—including administrators. Attackers can then trigger password resets to the new email and gain full account access, with the plugin additionally returning authentication cookies in the response for direct session hijacking.
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.
-
Identify if OTP-less plugin is installedNavigate to WordPress admin dashboard > Plugins and look for 'OTP-less One Tap Sign In' or check the plugins directory via file system for the otp-less folderAffected if The plugin is present in the WordPress installation
-
Determine installed plugin versionIn WordPress admin > Plugins > Installed Plugins, find the OTP-less entry and note the version number displayedAffected if The installed version falls within any vulnerable version range (compare against official vulnerability advisory)
-
Check for unauthorized email modificationsIn WordPress admin > Users, review the email address column for all user accounts, particularly administrators, and compare against known legitimate email addressesAffected if Any user account shows an email address that was not changed by the legitimate account owner
-
Inspect user account audit logsIf user logging plugins or WordPress activity logs are available, review recent user profile changes for unexpected email update eventsAffected if Recent email change events appear for users who did not make those changes
-
Review for unexpected authentication sessionsCheck browser cookie storage or WordPress session tables for authentication cookies that may have been returned in plugin API responsesAffected if Authentication cookies exist that were not obtained through normal login procedures
If the OTP-less plugin is installed and its version is within the vulnerable range, or if unauthorized email changes are detected in user accounts, the environment is likely affected.
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.
dbcve · scopedUpdate the plugin to the latest version immediately. Review user accounts for unauthorized email changes and reset passwords for all administrator accounts as a precautionary measure.
2.0.60 or later
- Update the OTP-less one tap Sign in plugin to version 2.0.60 or later
- After updating, verify that users with administrative privileges still have correct email addresses
- If any suspicious users were added or emails were changed, remove unauthorized accounts and restore legitimate administrator access
Generated from the published advisory — verify against the referenced sources before acting.
- 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-3746 — 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-3746 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