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

> Authenticated attackers can overwrite critical files via unrestricted file upload in WAGO e!DISPLAY devices, potentially leading to code execution.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7373-xjj5-q36p

## What is CVE-2018-12979?

CVE-2018-12979 is a medium-severity vulnerability in n/a, published on 12 Jul 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered on WAGO e!DISPLAY 762-3000 through 762-3003 devices with firmware before FW 02. Weak permissions allow an authenticated user to overwrite critical files by abusing the unrestricted file upload in the WBM.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 4 products.


Products: Wago 762-3000 Firmware, Wago 762-3001 Firmware, Wago 762-3002 Firmware, Wago 762-3003 Firmware.

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

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

## Is CVE-2018-12979 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-12979 exists.

Public exploit code:

- WAGO e!DISPLAY 7300T - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2018-12980](https://insights.sbomify.com/CVE-2018-12980/): File upload in n/a (high 8.8)
- [CVE-2018-12981](https://insights.sbomify.com/CVE-2018-12981/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-12979 is a medium-severity vulnerability in n/a, published on 12 Jul 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-12979 exists.

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

## Sources

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

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