# CVE-2026-19453: JetBackup 3.1.7.9 - 3.1.23.3 - Subscriber+ Privilege Escalation via Restore Admin User Selection

> A subscriber can gain administrator privileges after a site restore or migration due to missing role verification in JetBackup.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Sep 2026
- **Updated:** 2 Sep 2026
- **Also known as:** GHSA-qpph-f397-9mqv

## What is CVE-2026-19453?

CVE-2026-19453 is a high-severity vulnerability in Unknown JetBackup, published on 2 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The JetBackup  WordPress plugin before 3.1.23.5 does not verify the role or capabilities of the account it preserves across a restore or migration before granting it administrator privileges, allowing a subscriber-level user to gain administrator access after the site owner restores or migrates the site.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-19453 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19453 is a high-severity vulnerability in Unknown JetBackup, published on 2 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-19453 in the wild and no public exploit code.

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

## Sources

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

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