# CVE-2026-75903: Vulnity Security <= 1.4.3 - Unauthenticated Authentication Bypass to Administrator via Exposed Pairing Credentials

> Unauthenticated attackers can bypass authentication and gain administrator access by exploiting exposed pairing credentials in Nginx configurations.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-cpp4-39xq-w89m

## What is CVE-2026-75903?

CVE-2026-75903 is a high-severity authentication bypass vulnerability in manuelgalan Vulnity Security, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Vulnity Security plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 1.4.3 This is due to insufficient protection of the delegated-login pairing credential file on Nginx-based installations, where the plugin's generated server configuration snippet guards the wrong directory path. This makes it possible for unauthenticated attackers to retrieve the stored credentials, forge signed REST API requests, and log in as an administrator.

Weakness: CWE-287 (Improper Authentication)

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


## How do I fix CVE-2026-75903?

No fix has been published for CVE-2026-75903 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-75903 being exploited?

There is no known exploitation of CVE-2026-75903 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-75903 and fix it if it is affected.

What it is: CVE-2026-75903 is a high-severity authentication bypass vulnerability in manuelgalan Vulnity Security, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-75903 in the wild and no public exploit code.

Affected product: manuelgalan Vulnity Security. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-75903/ (Markdown: https://insights.sbomify.com/CVE-2026-75903/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-75903
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-75903
- OSV: https://osv.dev/vulnerability/CVE-2026-75903

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-75903/
Summaries are generated and may contain mistakes; the official description above is the record.