# CVE-2018-6881: Information disclosure in n/a

> Remote attackers can discover the full server path by sending an array value to a specific parameter in EmpireCMS.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-fc36-cvc7-f5jj

## What is CVE-2018-6881?

CVE-2018-6881 is a medium-severity vulnerability in Dedecms Dedecms, published on 12 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

EmpireCMS 6.6 allows remote attackers to discover the full path via an array value for a parameter to admin/tool/ShowPic.php.

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

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

It affects 2 products.


Products: Dedecms Dedecms, Phome Empirecms.

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

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

## Is CVE-2018-6881 being exploited?

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

## Other vulnerabilities in Dedecms Dedecms

- [CVE-2026-30643](https://insights.sbomify.com/CVE-2026-30643/): Code injection in n/a (critical 9.8)
- [CVE-2026-30694](https://insights.sbomify.com/CVE-2026-30694/): Code injection in n/a (critical 9.8)
- [CVE-2024-35510](https://insights.sbomify.com/CVE-2024-35510/): File upload in n/a (critical 9.8)
- [CVE-2024-35375](https://insights.sbomify.com/CVE-2024-35375/): File upload in n/a (critical 9.8)
- [CVE-2024-29661](https://insights.sbomify.com/CVE-2024-29661/): File upload in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-6881 is a medium-severity vulnerability in Dedecms Dedecms, published on 12 Feb 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-6881 in the wild and no public exploit code.

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

## Sources

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

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