# CVE-2025-8682: Newsup <= 5.0.10 - Missing Authorization to Authenticated (Subscriber+) Plugin Installation

> Unauthenticated attackers can install plugins due to missing capability checks, potentially leading to code execution and privilege escalation.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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:** 11 Oct 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-8qmq-qcpw-x7qq

## What is CVE-2025-8682?

CVE-2025-8682 is a medium-severity missing authorization vulnerability in themeansar Newsup, published on 11 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Newsup theme for WordPress is vulnerable to unauthorized plugin installation due to a missing capability check on the newsup_admin_info_install_plugin() function in all versions up to, and including, 5.0.10. This makes it possible for unauthenticated attackers to install the ansar-import plugin.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2025-8682 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-8682 is a medium-severity missing authorization vulnerability in themeansar Newsup, published on 11 Oct 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-8682 in the wild and no public exploit code.

Affected product: themeansar Newsup. 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-8682/ (Markdown: https://insights.sbomify.com/CVE-2025-8682/index.md)
```

## Sources

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

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