# CVE-2025-10915: Dreamer Blog <= 1.2 - Subscriber+ Arbitrary Plugin Installation

> Subscribers can install arbitrary plugins in the Dreamer Blog WordPress theme due to missing capability checks, potentially leading to code execution.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jan 2026
- **Updated:** 2 Apr 2026
- **Also known as:** GHSA-7h35-mm5q-hf4v

## What is CVE-2025-10915?

CVE-2025-10915 is a critical missing authorization vulnerability in Unknown Dreamer Blog, published on 13 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Dreamer Blog WordPress theme through 1.2 is vulnerable to arbitrary  installations due to a missing capability check.

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


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

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

## Is CVE-2025-10915 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10915 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10915 is a critical missing authorization vulnerability in Unknown Dreamer Blog, published on 13 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10915 exists.

Affected product: Unknown Dreamer Blog. 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-10915/ (Markdown: https://insights.sbomify.com/CVE-2025-10915/index.md)
```

## Sources

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

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