Skip to content
CVE-2026-129073: update miniOrange OTP Verification

CVE-2026-129073: update miniOrange OTP Verification

November 21, 2026

Patchstack rates CVE-2026-129073 Critical, with a CVSS 3.1 score of 9.8. Its CNA record dates public disclosure to November 18, 2026 and CVE record publication to November 20.

Match the package and correction

The affected WordPress package is miniorange-otp-verification. Versions through 5.6.1 are affected; the CNA explicitly recommends updating to the latest available version, at least 5.6.2. The official plugin listing currently offers 5.6.2 under the name miniOrange OTP Login, Verification and SMS Notifications.

Match the package identity before assigning this correction to an inventory entry. miniOrange publishes multiple products; this version floor does not establish the status of a different plugin or separately maintained edition.

Record the installed version and which ordinary site forms use OTP verification. Include separate WordPress instances and serving copies behind a load balancer. Preserve a recoverable database and file backup before updating, and retain the plugin’s configured delivery provider and form settings securely.

Deploy and check normal verification

Install the corrected release through the site’s supported plugin update or deployment process. Check its WordPress and PHP requirements before the maintenance window. If a packaging vendor supplies a backported fix, use its explicit CVE status and installed package build as the correction evidence.

Verify the installed plugin version after deployment. With an approved test account and a phone number or mailbox controlled by the test operator, check an ordinary configured verification flow. Confirm delivery through the intended provider and successful completion of the site’s normal form workflow. Keep real customer addresses out of testing and account for any message-delivery charges.

Check each deployed site that uses the plugin, rather than assuming one successful form check covers independent installations. Keep the update result and version evidence with the normal-flow check. Do not restore an older plugin copy during rollback without reassessing its security status.

Acknowledgements

This post was created with assistance from AI.

Last updated on