# CVE-2025-14478: Demo Importer Plus <= 2.0.9 - Authenticated (Author+) Blind XML External Entity Injection via SVG File Upload


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Jan 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-4qr6-cjv5-78xj

## What is CVE-2025-14478?

CVE-2025-14478 is a high-severity vulnerability in kraftplugins Demo Importer Plus, published on 17 Jan 2026. 

### Official description

The Demo Importer Plus plugin for WordPress is vulnerable to XML External Entity Injection (XXE) in all versions up to, and including, 2.0.9 via the SVG file upload functionality. This makes it possible for authenticated attackers, with Author-level access and above, to achieve code execution in vulnerable configurations. This only impacts sites on versions of PHP older than 8.0.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

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


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

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

## Is CVE-2025-14478 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14478 is a high-severity vulnerability in kraftplugins Demo Importer Plus, published on 17 Jan 2026. 
Exploitation: There is no known exploitation of CVE-2025-14478 in the wild and no public exploit code.

Affected product: kraftplugins Demo Importer Plus. 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-14478/ (Markdown: https://insights.sbomify.com/CVE-2025-14478/index.md)
```

## Sources

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

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