# CVE-2026-14812: Premium SEO - Unauthenticated Backdoor (Admin Creation / RCE / SSRF / Content Injection)

> Unauthenticated attackers can create hidden admin accounts and execute code via a malicious backdoor in the Premium SEO WordPress plugin.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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:** 6 Aug 2026
- **Updated:** 7 Aug 2026
- **Also known as:** GHSA-r59p-4mh6-5r64

## What is CVE-2026-14812?

CVE-2026-14812 is a critical authentication bypass vulnerability in Unknown Premium SEO, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Premium SEO WordPress plugin is malicious: it ships an unauthenticated backdoor that creates a hidden administrator account and, in some builds, also enables remote code execution, server-side request forgery and arbitrary front-end script/content injection, giving an unauthenticated attacker full control of the affected site.

Weakness: CWE-912 (Hidden Functionality)

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


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

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

## Is CVE-2026-14812 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-14812 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14812 is a critical authentication bypass vulnerability in Unknown Premium SEO, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-14812 exists.

Affected product: Unknown Premium SEO. 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-14812/ (Markdown: https://insights.sbomify.com/CVE-2026-14812/index.md)
```

## Sources

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

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