PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-110135 OTP Login & Register Woocommerce CVE debrief

The OTP Login & Register Woocommerce WordPress plugin before 2.7.3 does not adequately limit one-time-password verification attempts, allowing an unauthenticated attacker to bypass the limit and brute-force the short numeric login code, potentially leading to account takeovers without a password. Defenders should assess exposure and prioritize remediation to prevent such attacks. The vulnerability is tracked against a client-supplied value, enabling attackers to freely change and bypass the limit.

Vendor
OTP Login & Register Woocommerce
Product
WordPress plugin
CVSS
Unknown
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-16
Original CVE updated
2026-10-16
Advisory published
2026-10-16
Advisory updated
2026-10-16

Who should care

Defenders responsible for WordPress installations using the OTP Login & Register Woocommerce plugin should assess exposure and prioritize remediation to prevent account takeovers. Security teams and vulnerability management teams should review and implement additional security measures to prevent brute-force attacks on login codes.

Why it matters

Defenders should prioritize verifying and remediating this vulnerability in their WordPress installations to prevent account takeovers.

  • An unauthenticated attacker can bypass the limit and brute-force the short numeric login code to take over an account without its password.

Technical summary

The OTP Login & Register Woocommerce WordPress plugin before 2.7.3 does not adequately limit one-time-password verification attempts, because the attempt limit is tracked against a value the client itself supplies and can change freely, allowing an unauthenticated attacker to bypass the limit and brute-force the short numeric login code to take over an account without its password. The plugin's implementation enables an attacker to bypass security measures and gain unauthorized access to accounts. Defenders should prioritize verifying and remediating this vulnerability in their WordPress installations.

Defensive priority

Defenders should prioritize verifying and remediating this vulnerability in their WordPress installations.

Recommended defensive actions

  • Verify the version of the OTP Login & Register Woocommerce WordPress plugin and update to 2.7.3 or later.
  • Implement additional security measures to prevent brute-force attacks on login codes.
  • Review compensating controls for exposed systems while remediation is scheduled and verified.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented.
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Evidence notes

The vulnerability is described in the CVE record and a source reference from WPScan. The CVE record was published on 2026-10-16T07:17:10.683Z and has not been modified since then. The source reference from WPScan provides additional details about the vulnerability. Defenders should verify the version of the OTP Login & Register Woocommerce WordPress plugin and update to 2.7.3 or later.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-110135 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-110135

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-110135 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-110135

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.