# CVE-2026-115251: Duplicator 1.5.17 - Multisite Subsite Admin+ Network-Wide PHP Code Execution via One-Click Upgrade


- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 25 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-j9mp-rgph-hchj

## What is CVE-2026-115251?

CVE-2026-115251 is a high-severity vulnerability in Unknown Duplicator, published on 25 Oct 2026. 

### Official description

The Duplicator  WordPress plugin before 5.0.0 does not restrict its one-click upgrade routine to users allowed to install Duplicator  WordPress plugin before 5.0.0, and additionally exposes the routine without authentication, allowing an administrator of a multisite child site who is not a network administrator to install and run arbitrary PHP in the network-wide shared Duplicator  WordPress plugin before 5.0.0 directory.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-115251 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-115251 is a high-severity vulnerability in Unknown Duplicator, published on 25 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115251 in the wild and no public exploit code.

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

## Sources

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

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