# CVE-2026-12082: Missing authorization in Praison AI SEO

> Unauthenticated attackers can modify post permalinks and read plugin configuration data due to missing authorization checks in REST API routes.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jul 2026
- **Updated:** 23 Jul 2026
- **Also known as:** GHSA-mr6p-pxvc-7864

## What is CVE-2026-12082?

CVE-2026-12082 is a high-severity missing authorization vulnerability in Unknown Praison AI SEO, published on 23 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Praison AI SEO WordPress plugin before 5.0.7 does not perform authorization checks on several of its REST API routes, allowing unauthenticated users to modify the permalink of any published post and to read Praison AI SEO WordPress plugin before 5.0.7 configuration data.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-12082 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12082 is a high-severity missing authorization vulnerability in Unknown Praison AI SEO, published on 23 Jul 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-12082 exists.

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

## Sources

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

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