# CVE-2025-47695: WordPress Blog Designer PRO plugin <= 3.4.7 - Authenticated Non-Arbitrary Local File Inclusion vulnerability

> Authenticated attackers can exploit a local file inclusion flaw in the Blog Designer PRO plugin to read arbitrary files on the server.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/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:** 9 Sep 2025
- **Updated:** 12 May 2026
- **Also known as:** GHSA-7vvx-j9w3-8qr5

## What is CVE-2025-47695?

CVE-2025-47695 is a high-severity path traversal vulnerability in solwin Blog Designer PRO, published on 9 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in solwin Blog Designer PRO blog-designer-pro.This issue affects Blog Designer PRO: from n/a through <= 3.4.7.

Weakness: CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program)

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


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

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

## Is CVE-2025-47695 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-47695 is a high-severity path traversal vulnerability in solwin Blog Designer PRO, published on 9 Sep 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-47695 in the wild and no public exploit code.

Affected product: solwin Blog Designer PRO. 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-47695/ (Markdown: https://insights.sbomify.com/CVE-2025-47695/index.md)
```

## Sources

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

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