# CVE-2018-11311: Hardcoded credentials in n/a

> Remote attackers can access the FTP server and upload files or list directories using hardcoded credentials in the mySCADA myPRO gateway.

- **Severity:** Critical 9.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 20 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-p3gj-f53r-qh79

## What is CVE-2018-11311?

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

### Official description

A hardcoded FTP username of myscada and password of Vikuk63 in 'myscadagate.exe' in mySCADA myPRO 7 allows remote attackers to access the FTP server on port 2121, and upload files or list directories, by entering these credentials.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 1 product.


Products: Myscada Mypro.

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

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

## Is CVE-2018-11311 being exploited?

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

Public exploit code:

- CVE-2018-11311 | mySCADA myPRO 7 Hardcoded FTP Username and Password Vulnerability (github_poc): https://github.com/EmreOvunc/mySCADA-myPRO-7-Hardcoded-FTP-Username-and-Password
- mySCADA myPRO 7 - Hardcoded Credentials (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2025-24865](https://insights.sbomify.com/CVE-2025-24865/): mySCADA myPRO Manager Missing Authentication for Critical Function (critical 10.0)
- [CVE-2021-22657](https://insights.sbomify.com/CVE-2021-22657/): mySCADA myPRO (critical 10.0)
- [CVE-2021-23198](https://insights.sbomify.com/CVE-2021-23198/): mySCADA myPRO (critical 10.0)
- [CVE-2021-43981](https://insights.sbomify.com/CVE-2021-43981/): mySCADA myPRO (critical 10.0)
- [CVE-2021-43984](https://insights.sbomify.com/CVE-2021-43984/): mySCADA myPRO (critical 10.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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