Patchstack says an unauthenticated attacker can bypass login or enter as another user without that user's password. The published classification is authentication bypass through an alternate path or channel (CWE-288).Patchstack lists plugin versions through 5.6.1 as affected and 5.6.2 as the patched release. This is a plugin issue, so administrators should inventory the installed plugin version on each WordPress site. The public record does not describe the exact vulnerable code path or any additional configuration condition.
What it allows
How Does CVE-2026-129073 Affect Authentication?
Patchstack classifies the issue as an alternate-path authentication bypass and says it requires no prior account. Its public entry says an attacker could pass the login barrier or impersonate another user without a password. It does not publish enough mechanism detail to identify a particular request or endpoint.
For a site owner, the relevant exposure is an installed, active miniOrange OTP Verification plugin at version 5.6.1 or earlier. We recommend treating Internet-facing login flows as the first review priority. For related product information, see the Vulnerability Intelligence platform.
What Is Known About Exploitation?
Patchstack labels the entry as known to be exploited, and its CNA record carries a known-exploited tag. CISA's ADP assessment dated 20 November 2026 lists exploitation as none. CVE-2026-129073 was absent from CISA KEV catalog version 2026.11.20, so these labels should not be treated as one confirmed incident count.
From 24 August through 22 November 2026, Brandefense Blackhole counted two dark-chat posts matching this CVE. The measured unit is posts, not attackers or incidents. A GitHub search captured on 21 November 2026 found one public repository named for the CVE; its name alone does not establish a working exploit.
Who is affected
Which miniOrange OTP Verification Versions Are Affected?
Patchstack and the CVE record identify versions through 5.6.1 as affected and version 5.6.2 as the fix. The CVE record uses an open lower boundary, so it does not establish a precise first vulnerable release. Check each site's installed plugin version against the advisory before scheduling the update.
Patchstack does not list a special WordPress configuration needed for the flaw. That is an absence of a published condition, not proof that every deployment has an identical attack path. Record the plugin state, version and site owner in the patch management process.
The vulnerability intelligence glossary explains how version and exposure evidence support prioritization. For this CVE, prioritize sites where the affected plugin is active and reachable. Keep a separate record of sites where the plugin is inactive or absent.
Timeline
-
2026-11-11
Patchstack records the vulnerability report from AndrewN.
-
2026-11-18
Patchstack made its vulnerability entry public and identified version 5.6.2 as patched.
-
2026-11-20
The CVE record was published. CISA's ADP assessment recorded exploitation as none, while Patchstack's CNA record carried a known-exploited tag.
What to do
-
Inventory affected sites
List WordPress sites with the miniOrange OTP Verification plugin and record each installed version. Prioritize active versions through 5.6.1, particularly on Internet-facing sites.
-
Update the plugin
Install version 5.6.2 or later, as Patchstack and the CVE record direct. If the update is unavailable, ask the site owner or hosting provider to arrange remediation.
-
Verify the running version
After updating, confirm that WordPress reports miniOrange OTP Verification 5.6.2 or later on every affected site. Record the verification date and any site still on an older release.
-
Review authentication activity
As a precaution, review account and login activity around exposed sites for unexpected access. Investigate anomalies with site-specific evidence; a log anomaly alone cannot attribute activity to this CVE.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-129073 in Brandefense Atlas
The Atlas record of CVE-2026-129073: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
What is CVE-2026-129073?
It is an authentication bypass in the miniOrange OTP Verification WordPress plugin. Patchstack classifies it as an alternate-path or channel flaw, CWE-288.
Which version fixes CVE-2026-129073?
Patchstack and the CVE record identify version 5.6.2 as patched. Verify that each affected WordPress site actually runs 5.6.2 or later after updating.
Is CVE-2026-129073 in CISA KEV?
It was absent from CISA KEV catalog version 2026.11.20. Patchstack's exploited label and CISA's separate ADP assessment differ, so review each source by date and scope.
Does this flaw require an existing account?
Patchstack marks the required privilege as unauthenticated. Its public entry does not specify an additional configuration prerequisite or the exact vulnerable request path.
Sources
- miniOrange OTP Verification Broken AuthenticationPatchstack
- CVE-2026-129073 RecordPatchstack via CVE Program
- Known Exploited Vulnerabilities CatalogCISA