# CVE-2018-9126: Path traversal in n/a

> Remote attackers can read the web.config file to discover database credentials via a path traversal vulnerability in the DNNArticle module.

- **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:** 4 Apr 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7jcf-pp7q-q98w

## What is CVE-2018-9126?

CVE-2018-9126 is a critical path traversal vulnerability in n/a, published on 4 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The DNNArticle module 11 for DNN (formerly DotNetNuke) allows remote attackers to read the web.config file, and consequently discover database credentials, via the /GetCSS.ashx/?CP=%2fweb.config URI.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Zldnn Dnnarticle.

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

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

## Is CVE-2018-9126 being exploited?

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

Public exploit code:

- DotNetNuke DNNarticle Module 11 - Directory Traversal (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2013-5117](https://insights.sbomify.com/CVE-2013-5117/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-9126 is a critical path traversal vulnerability in n/a, published on 4 Apr 2018. 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-9126 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-9126/ (Markdown: https://insights.sbomify.com/CVE-2018-9126/index.md)
```

## Sources

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

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