miniOrange SAML flaws exploited for WordPress admin access

miniOrange SAML flaws exploited for WordPress admin access

Two unauthenticated flaws in the miniOrange SAML plugin are being actively exploited to sign in as any WordPress user, including admins. Patch now.

Attackers are actively trying to exploit two severe unauthenticated flaws in the miniOrange SAML 2.0 Single Sign On plugin for WordPress. This plugin allows websites to accept logins from an external identity provider through SAML, short for Security Assertion Markup Language, a standard for exchanging authentication information between a service and an identity provider. Because the flaws require no prior login or password, an attacker can sign in as any existing WordPress user, including site administrators. Patchstack, a WordPress security company, disclosed the vulnerabilities and credited the DigitalOcean security team for reporting them.

The two issues are tracked as CVE-2026-61979 and CVE-2026-15981. CVE identifiers are unique labels for publicly known security problems, and CVSS scores measure severity on a scale from 0 to 10. The first vulnerability, CVE-2026-61979, has a CVSS score of 8.1 and is an unauthenticated privilege escalation vulnerability caused by signature algorithm confusion. It was fixed in version 17.0.5 for the Standard edition. The second vulnerability, CVE-2026-15981, has a CVSS score of 9.8, which is rated critical, and is an authentication bypass that occurs because the plugin accepts malformed signatures as valid. It was fixed in version 17.0.6 for the Standard edition.

The most severe issue, CVE-2026-15981, sits in a function called mo_saml_validate_signature(). According to the description on CVE.org, that function performs a loose boolean check on the raw tri-state integer returned by PHP's openssl_verify() function. PHP is the programming language WordPress is built on, and openssl_verify() is a routine that checks the cryptographic signature of a message. The function can return 1 for a valid signature, 0 for an invalid signature, or -1 when an error occurs during processing. Because the plugin treats that return value loosely, the error value -1 is evaluated as true, which is mistaken for a successful signature check. This makes it possible for an unauthenticated attacker to log in as any existing WordPress user, including administrators, by sending a specially crafted SAMLResponse containing an attacker-controlled NameID, which is the identifier that says who the user is, and a deliberately malformed signature value that causes an OpenSSL processing error. As a result, the verification is skipped and the WordPress function wp_set_auth_cookie() is called for the targeted account, giving the attacker a valid administrator session.

Patchstack says the cloud infrastructure provider DigitalOcean discovered the flaws after noticing an anomalous WordPress administrator session attempt from outside its trusted network. The attacker had already used the bypass to obtain a WordPress admin session cookie, but was stalled because the admin panel operations themselves were restricted to the trusted network. Patchstack also shared the IP addresses from which the scanning activity has been recorded: 207.211.214.41, 79.127.224.14, 102.91.71.83, 162.243.116.148, 84.201.6.54, and 64.225.25.188. The security company said the spread suggests opportunistic scanning rather than a targeted campaign, with whoever is running it throwing the exploit at every site with the plugin installed without checking which edition or version is behind it.

WordPress site owners who use the plugin should update to the latest fixed version immediately, especially because proof-of-concept code is already available that chains the two flaws together to obtain admin privileges and take control of susceptible sites. The fixes are in version 17.0.6 for the Standard edition, and users should check their WordPress dashboard for available updates. Because attackers do not need to know a password and the exploit can be launched over the internet, any site with the vulnerable plugin is a potential target until patched. Patchstack's finding that the scanning appears opportunistic means many site owners may already be being probed, even if their specific edition or configuration was not deliberately chosen.

Once an attacker obtains administrator access, they can take control of the site, change content, install malicious code, or lock out the legitimate owner. This makes the flaw especially serious for businesses that rely on WordPress for customer-facing pages or internal tools. For website owners who would rather have WordPress maintenance handled by a provider, AEU Hosting offers managed WordPress hosting secured end to end. Site owners can also review administrator accounts and access logs for suspicious login activity from the IP addresses listed above and enable two-factor authentication as an extra layer of protection.

How to Protect Yourself

  1. If your WordPress site uses the miniOrange SAML 2.0 Single Sign On plugin, log in to your WordPress dashboard and update it to version 17.0.6 or the latest available.
  2. Check the list of administrator accounts in your WordPress site and remove any you do not recognize, then change all admin passwords.
  3. Turn on two-factor authentication for every administrator account so a stolen password or session is not enough to get in.
  4. Look at your site's login or activity logs for sign-ins from the IP addresses listed in this article and block those addresses if your hosting panel allows it.
  5. If you no longer use the miniOrange SAML plugin, deactivate and delete it from your WordPress site.
  6. Set WordPress core, plugins and themes to update automatically where possible.

Vulnerabilities & Fixes

  • CVE-2026-15981 Authentication bypass vulnerability in miniOrange SAML 2.0 Single Sign On plugin caused by accepting malformed signatures as valid, fixed in version 17.0.6 for the Standard edition. View the fix & details →
  • CVE-2026-61979 Unauthenticated privilege escalation vulnerability in miniOrange SAML 2.0 Single Sign On plugin caused by signature algorithm confusion, fixed in version 17.0.5 for the Standard edition. View the fix & details →

Terms Explained

  • SAML A standard way for websites to let you sign in using a single login from another company, so you do not need a separate password.
  • SSO Single sign-on, a feature that lets you use one set of login details for several different services.
  • Authentication bypass A security mistake that lets someone get into a system without proving who they are.
  • CVSS A number from 0 to 10 that rates how serious a software vulnerability is, with higher numbers meaning more severe.
  • CVE A unique code given to a publicly known software security problem so everyone can refer to the same issue.
  • Plugin A piece of software you add to a website to give it extra features, such as the ability to accept logins from another service.
  • Signature In computer security, a digital mark that proves a message really comes from the person or system it claims to be from.
  • NameID A piece of a login message that identifies which user is trying to sign in.

Related AEU services

  • AEU Panel Managed hosting control panel
  • AEU-I IT and security consulting