External risk intelligence

Auth Armor WordPress Plugin Credential Leak and Account Takeover

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-110960

The vulnerability affects a WordPress plugin, which is a type of web application component commonly deployed on public-facing websites. Because the plugin handlers are accessible to unauthenticated users via the web interface, the attack surface is frequently exposed directly to the internet in typical WordPress site deployments.

Authentication Bypass

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability has been identified in a WordPress plugin that could allow unauthorized access to administrator accounts. This issue affects the Auth Armor plugin, which, through improper authentication checks, can expose API credentials and enable account takeover by unauthenticated users. The primary concern is confirming whether this plugin is in use and if it is exposed to the internet.

  • Unauthenticated users can steal credentials and take over accounts.
  • Protects against unauthorized administrative access and data breaches.
  • Confirm use and external exposure of the Auth Armor plugin.

Attack Path

How an attacker could exploit the issue

A potential attacker can access several functions of the Auth Armor WordPress plugin without logging in. This exposure allows them to steal API credentials, which can then be used to reset an administrator's account and gain full control of the website.

  • Unauthenticated access to plugin functions.
  • Leaking API credentials to reset administrator accounts.
  • Full administrative account takeover.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an unauthenticated attacker to access and steal stored API credentials from a WordPress site, and then reset an administrator's account enrollment to take over that administrator account. This could happen when the Auth Armor plugin is installed and active on a WordPress site.

  • Site API credentials could be exposed.
  • Unauthenticated access to specific plugin handlers.
  • Administrator account takeover is possible.

Operational Fix

Recommended remediation, mitigation, and detection steps

Website owners and platform teams are likely responsible for addressing this vulnerability. The first step is to inventory all WordPress sites, confirm exposure of the Auth Armor plugin, and identify the business criticality of each affected instance to prioritize remediation efforts.

  • WordPress site owners must own remediation.
  • Verify plugin exposure and admin account reachability.
  • Plan maintenance to coordinate plugin updates.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the Auth Armor plugin for WordPress?

Auth Armor is a plugin designed to manage authentication security for WordPress websites. It helps site administrators integrate secure login methods by storing specific API credentials used to communicate with authentication services. Because it sits at the intersection of a site's login process and external verification, it must maintain strict control over who can access its underlying communication handlers.

How does CVE-2026-110960 enable account takeover?

This vulnerability is classified as Improper Authentication (CWE-287). It occurs because the plugin fails to verify user identity for certain internal functions. By interacting with these unprotected handlers, an unauthorized person can extract the site's stored API credentials. With those credentials in hand, they can trigger a reset of the administrator's enrollment, effectively bypassing standard login protections to seize full control of the account.

Do I need to be logged in to trigger this vulnerability?

No. The flaw specifically affects handlers that are accessible to users who have not logged in. An attacker does not need any pre-existing site credentials or administrative permissions to initiate this exploit. The vulnerability is triggered simply by reaching the exposed plugin functions over the network; it does not require prior knowledge of the site's configuration or active user sessions.

Why is this vulnerability a concern for my website?

Halo Surface Signal notes that since the Auth Armor plugin functions are accessible via the web, they are often directly exposed to the internet. Because WordPress sites are typically public-facing, this vulnerability creates a high risk of remote exploitation. If your site uses this plugin, the attack surface is likely available to anyone on the internet who can send a web request to your server.

What should I do first if I use Auth Armor?

Begin by conducting an immediate inventory to confirm if the Auth Armor plugin is installed and active on your WordPress instances. Once you have identified all affected sites, determine their business criticality to prioritize your response. Coordinate with your team to plan the necessary maintenance, which includes checking for plugin updates that resolve these authentication flaws.

References