# CVE-2025-12481: WP Duplicate Page <= 1.7 - Missing Authorization to Authenticated (Contributor+) Sensitive Information Disclosure

> Authenticated contributors can modify plugin settings to bypass restrictions and view sensitive password-protected posts.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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:** 18 Nov 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-xqvw-6qp4-5g2p

## What is CVE-2025-12481?

CVE-2025-12481 is a medium-severity missing authorization vulnerability in ninjateam WP Duplicate Page, published on 18 Nov 2025. 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 Missing Authorization in all versions up to, and including, 1.7. This is due to the plugin not properly verifying that a user is authorized to perform an action in the 'saveSettings' function. This makes it possible for authenticated attackers, with Contributor-level access and above, to modify plugin settings that control role capabilities, and subsequently exploit the misconfigured capabilities to duplicate and view password-protected posts containing sensitive information.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2025-12481 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-12481 is a medium-severity missing authorization vulnerability in ninjateam WP Duplicate Page, published on 18 Nov 2025. 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-12481 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-12481/ (Markdown: https://insights.sbomify.com/CVE-2025-12481/index.md)
```

## Sources

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

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