# CVE-2018-14485: XML external entity in n/a

> An attacker can exploit an XML External Entity vulnerability in BlogEngine.NET to read sensitive files or cause denial of service.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 7 May 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-j2c4-rr9q-8j5c

## What is CVE-2018-14485?

CVE-2018-14485 is a critical vulnerability in n/a, published on 7 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

BlogEngine.NET 3.3 allows XXE attacks via the POST body to metaweblog.axd.

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

## Which versions are affected by CVE-2018-14485?

It affects 1 product.


Products: Blogengine Blogengine.net.

## How do I fix CVE-2018-14485?

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

## Is CVE-2018-14485 being exploited?

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

Public exploit code:

- BlogEngine 3.3 - XML External Entity Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2023-33404](https://insights.sbomify.com/CVE-2023-33404/): File upload in n/a (critical 9.8)
- [CVE-2022-41417](https://insights.sbomify.com/CVE-2022-41417/): Missing authorization in n/a (critical 9.8)
- [CVE-2019-6714](https://insights.sbomify.com/CVE-2019-6714/): Path traversal in n/a (critical 9.8)
- [CVE-2022-25591](https://insights.sbomify.com/CVE-2022-25591/): Path traversal in n/a (critical 9.1)
- [CVE-2019-10720](https://insights.sbomify.com/CVE-2019-10720/): Path traversal in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-14485 and fix it if it is affected.

What it is: CVE-2018-14485 is a critical vulnerability in n/a, published on 7 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-14485 in the wild and no public exploit code.

Affected product: n/a. 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-2018-14485/ (Markdown: https://insights.sbomify.com/CVE-2018-14485/index.md)
```

## Sources

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

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