# CVE-2018-11638: File upload in n/a

> Authenticated attackers can upload malicious files to the web root in Dialogic PowerMedia XMS, leading to remote code execution.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-gf7q-r3m3-52hf

## What is CVE-2018-11638?

CVE-2018-11638 is a high-severity vulnerability in n/a, published on 3 Jul 2018. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Unrestricted Upload of a File with a Dangerous Type in the administrative console in Dialogic PowerMedia XMS through 3.5 allows remote authenticated users to upload malicious code to the web root to gain code execution.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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

It affects 1 product.


Products: Dialogic Powermedia Xms.

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

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

## Is CVE-2018-11638 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-11635](https://insights.sbomify.com/CVE-2018-11635/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2018-11641](https://insights.sbomify.com/CVE-2018-11641/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2018-11640](https://insights.sbomify.com/CVE-2018-11640/): XML external entity in n/a (critical 9.1)
- [CVE-2018-11636](https://insights.sbomify.com/CVE-2018-11636/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2018-11643](https://insights.sbomify.com/CVE-2018-11643/): SQL injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-11638 is a high-severity vulnerability in n/a, published on 3 Jul 2018. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-11638 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-11638/ (Markdown: https://insights.sbomify.com/CVE-2018-11638/index.md)
```

## Sources

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

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