# CVE-2026-5722: MoreConvert Pro <= 1.9.14 - Authentication Bypass via Waitlist Guest Verification Token Reuse

> Unauthenticated attackers can bypass authentication and take over accounts, including administrators, by reusing guest verification tokens in the MoreConvert Pro plugin.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 May 2026
- **Updated:** 5 May 2026
- **Also known as:** GHSA-m5qv-996f-g5rh

## What is CVE-2026-5722?

CVE-2026-5722 is a critical authentication bypass vulnerability in MoreConvert Pro, published on 5 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The 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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-5722?


## How do I fix CVE-2026-5722?

No fix has been published for CVE-2026-5722 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-5722 being exploited?

There is no known exploitation of CVE-2026-5722 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-5722 and fix it if it is affected.

What it is: CVE-2026-5722 is a critical authentication bypass vulnerability in MoreConvert Pro, published on 5 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-5722 in the wild and no public exploit code.

Affected product: MoreConvert Pro. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-5722/ (Markdown: https://insights.sbomify.com/CVE-2026-5722/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-5722
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-5722
- OSV: https://osv.dev/vulnerability/CVE-2026-5722

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-5722/
Summaries are generated and may contain mistakes; the official description above is the record.