Skip to main content
Menu
CVEs

miniorange otp verification authentication bypass in login checks

CVE-2026-129073Published , updated

9.8CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 5.6.2
Who is exposed
Not reported

Summary

Authentication bypass in the miniOrange miniorange otp verification plugin lets an attacker get past login checks by using an alternate path or channel. It can be reached remotely, without logging in.

Written by a model

Original description

Authentication Bypass Using an Alternate Path or Channel vulnerability in miniOrange miniorange otp verification miniorange-otp-verification allows Authentication Abuse.This issue affects miniorange otp verification: from n/a through 5.6.1.

Who should check

Teams running the WordPress miniorange otp verification plugin version 5.6.1 or earlier

“WordPress miniorange otp verification Plugin <= 5.6.1 is vulnerable”

patchstack.com

What to do

Upgrade to a fixed version: 5.6.2.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-129073 (WordPress miniorange otp verification plugin <= 5.6.1 - Broken Authentication vulnerability), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129073 (entry last updated 2026-11-20):
Affected:
- miniOrange miniorange otp verification: fixed in 5.6.2
Fixed versions: 5.6.2.
Conditions (all must be true for the bug to be hit):
- WordPress miniorange otp verification plugin version 5.6.1 or earlier (source: https://patchstack.com/database/wordpress/plugin/miniorange-otp-verification/vulnerability/wordpress-miniorange-otp-verification-plugin-5-6-1-broken-authentication-vulnerability?_s_id=cve)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-129073 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129073 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/plugin/miniorange-otp-verification/vulnerability/wordpress-miniorange-otp-verification-plugin-5-6-1-broken-authentication-vulnerability?_s_id=cve
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129073
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129073"}.

Affected versions

cve.now Index

30Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 9.8, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 35 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now
  4. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: total

  5. Record last updated

Evidence 3

Questions about CVE-2026-129073

Is CVE-2026-129073 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

The plugin's broken authentication lets an attacker bypass the login system or log in as other users without their password.

Source: patchstack.com

Which versions are affected by CVE-2026-129073?

miniorange-otp-verification: through 5.6.1 (fixed in 5.6.2).

Source: cve.now feed data

Am I affected, and how do I check?

Versions 5.6.1 and earlier of the miniOrange OTP Verification plugin for WordPress are affected. To check your version, look at the plugin version shown on the WordPress Plugins screen.

Source: patchstack.com

How do I fix CVE-2026-129073?

Update the miniOrange OTP Verification plugin to version 5.6.2 or later, which the vendor states resolves the vulnerability.

Source: patchstack.com

No corrections so far. Something wrong on this page? Report an error.