# CVE-2025-69293: WordPress Final User plugin <= 1.2.5 - Privilege Escalation vulnerability

> Attackers can escalate privileges due to incorrect privilege assignment in the Final User WordPress plugin.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jan 2026
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-6hh3-55pq-pgwq

## What is CVE-2025-69293?

CVE-2025-69293 is a high-severity vulnerability in e-plugins Final User, published on 22 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Incorrect Privilege Assignment vulnerability in e-plugins Final User final-user allows Privilege Escalation.This issue affects Final User: from n/a through <= 1.2.5.

Weakness: CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2025-69293?


## How do I fix CVE-2025-69293?

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

## Is CVE-2025-69293 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-69293 and fix it if it is affected.

What it is: CVE-2025-69293 is a high-severity vulnerability in e-plugins Final User, published on 22 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-69293 in the wild and no public exploit code.

Affected product: e-plugins Final User. 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-2025-69293/ (Markdown: https://insights.sbomify.com/CVE-2025-69293/index.md)
```

## Sources

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

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