PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-81583 My Login CVE debrief

The My Login WordPress plugin before 7.2.0 does not enforce the network's registration setting when processing site signups on multisite installations, allowing users with a subscriber account, and unauthenticated users on some networks, to create new sites and be granted administrator over them. This vulnerability has significant implications for WordPress multisite administrators and users with subscriber accounts, as it could lead to unauthorized site creation and administration. It is essential to review and update the My Login WordPress plugin to version 7.2.0 or later and restrict site signups on multisite installations to authorized users.

Vendor
My Login
Product
My Login WordPress plugin
CVSS
MEDIUM 5.4
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-02
Original CVE updated
2026-09-03
Advisory published
2026-09-02
Advisory updated
2026-09-03

Who should care

WordPress multisite administrators, security teams, and users with subscriber accounts should review and update the My Login WordPress plugin to version 7.2.0 or later. They should also restrict site signups on multisite installations to authorized users and monitor for suspicious site creation activity.

Technical summary

The My Login WordPress plugin before 7.2.0 does not enforce the network's registration setting when processing site signups on multisite installations. This allows users with a subscriber account, and unauthenticated users on some networks, to create new sites and be granted administrator privileges over them. The vulnerability has a CVSS score of 5.4 and is classified as MEDIUM severity. Affected product deployments should be verified, and official advisories should be reviewed to validate affected scope, severity, and vendor guidance. Defenders should plan vendor-supported updates or mitigations through normal change control where exposure is confirmed and monitor for suspicious site creation activity.

Defensive priority

Medium priority due to potential for site creation and admin privileges

Recommended defensive actions

  • Review and update My Login WordPress plugin to version 7.2.0 or later
  • Restrict site signups on multisite installations to authorized users
  • Monitor for suspicious site creation activity
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

Evidence from WPScan indicates vulnerability in My Login WordPress plugin before 7.2.0. Official CVE and NVD records provide additional context. The vulnerability allows users with a subscriber account and unauthenticated users on some networks to create new sites and be granted administrator privileges over them. Defenders should verify affected product deployments, review official advisories, and plan vendor-supported updates or mitigations.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-81583 CVE Program record

    Publisher, destination, and source semantics verified

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

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

  • CVE-2026-81583 NVD vulnerability detail

    Publisher, destination, and source semantics verified

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

    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.