# CVE-2025-14001: WP Duplicate Page <= 1.8 - Missing Authorization to Authenticated (Contributor+) Arbitrary Post Duplication

> Authenticated contributors can bypass role restrictions to duplicate arbitrary posts and orders, potentially exposing sensitive data or causing duplicate fulfillments.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **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:** 13 Jan 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-crjh-4642-9w67

## What is CVE-2025-14001?

CVE-2025-14001 is a medium-severity missing authorization vulnerability in ninjateam WP Duplicate Page, published on 13 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WP Duplicate Page plugin for WordPress is vulnerable to unauthorized modification of data due to missing capability checks on the 'duplicateBulkHandle' and 'duplicateBulkHandleHPOS' functions in all versions up to, and including, 1.8. This makes it possible for authenticated attackers, with Contributor-level access and above, to duplicate arbitrary posts, pages, and WooCommerce HPOS orders even when their role is explicitly excluded from the plugin's "Allowed User Roles" setting, potentially exposing sensitive information and allowing duplicate fulfillment of WooCommerce orders.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2025-14001 being exploited?

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

Public exploit code:

- Patch: Provider credential leak (Terraform) (github_poc): https://github.com/gduma-phData/patch-CVE-2025-14001

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14001 is a medium-severity missing authorization vulnerability in ninjateam WP Duplicate Page, published on 13 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-14001 in the wild and no public exploit code.

Affected product: ninjateam WP Duplicate Page. 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-14001/ (Markdown: https://insights.sbomify.com/CVE-2025-14001/index.md)
```

## Sources

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

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