CVE-2026-5722
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 MoreConvert Pro plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 1.9.14. This is due to the guest waitlist verification flow not invalidating or regenerating verification tokens when the customer email address is changed. This makes it possible for unauthenticated attackers to authenticate as existing users, including administrators, by obtaining a valid guest verification token for an attacker-controlled email, changing the same guest customer email to the target account email through the public waitlist flow, and then using the original verification link.
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 MoreConvert Pro WordPress plugin has a critical authentication bypass in its guest waitlist verification flow. The vulnerability stems from the plugin not invalidating or regenerating verification tokens when a customer email address is changed, allowing unauthenticated attackers to hijack existing user accounts including administrators by obtaining a guest verification token, changing the associated email to a target account, then using the original token to authenticate as that user.
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 MoreConvert Pro plugin installation and versionIn WordPress admin, go to Plugins > Installed Plugins and locate MoreConvert Pro. Note the version number displayed, or check the plugin header file via file system at /wp-content/plugins/moreconvert-pro/Affected if The installed version is 1.9.14 or lower, or if the version cannot be determined (plugin may be outdated)
-
Confirm guest waitlist feature is activeAccess the plugin settings page in WordPress admin (usually under MoreConvert settings or a dedicated waitlist menu item). Look for guest waitlist or waitlist verification settings. Check if the waitlist functionality is enabled.Affected if The guest waitlist verification feature is enabled in the plugin configuration
-
Review existing waitlist entries for suspicious activityAccess the plugin's waitlist management interface (typically found in WordPress admin under the plugin's menu). Examine the list of registered emails and their associated verification tokens/status. Look for unexpected email changes or tokens associated with high-privilege accounts.Affected if There are waitlist entries where email addresses may have been changed, or tokens exist for administrative accounts
-
Audit WordPress user accounts for unauthorized accessIn WordPress admin, go to Users > All Users. Review user accounts, particularly administrators, for any suspicious login activity, password changes, or added capabilities. Check user metadata for any unusual waitlist-related fields.Affected if Any administrator account shows recent unexpected changes or the account was created/modified without legitimate admin action
A user is affected if the MoreConvert Pro plugin version is 1.9.14 or lower AND the guest waitlist feature is enabled in their WordPress 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 dataUpdate the MoreConvert Pro plugin to a version newer than 1.9.14, or disable the plugin entirely until a patched version is available.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5722 — 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-2026-5722 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