# CVE-2025-10896: Multiple Plugins <= Multiple Versions - Missing Authorization to Authenticated (Subscriber+) Arbitrary Plugin Upload

> Authenticated subscribers can upload arbitrary plugins due to missing authorization checks, potentially leading to remote code execution on WordPress sites.

- **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:** 4 Nov 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-rw6r-rw4v-3j2m

## What is CVE-2025-10896?

CVE-2025-10896 is a high-severity missing authorization vulnerability in litonice13 Content Locker for Elementor, published on 4 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple plugins for WordPress with the Jewel Theme Recommended Plugins Library are vulnerable to Unrestricted Upload of File with Dangerous Type via arbitrary plugin installation in all versions up to, and including, 1.0.2.3. This is due to missing capability checks on the '*_recommended_upgrade_plugin' function which allows arbitrary plugin URLs to be installed. This makes it possible for authenticated attackers with subscriber-level access and above to upload arbitrary plugin packages to the affected site's server via a crafted plugin URL, which may make remote code execution possible.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2025-10896 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10896 is a high-severity missing authorization vulnerability in litonice13 Content Locker for Elementor, published on 4 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-10896 in the wild and no public exploit code.

Affected product: litonice13 Content Locker for Elementor. 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-10896/ (Markdown: https://insights.sbomify.com/CVE-2025-10896/index.md)
```

## Sources

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

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