CVE Intelligence
Skip to main content
HIGHpublic exploit

CVE-2025-22896

CVE-2025-22896 — mySCADA myPRO Manager Cleartext Storage of Sensitive Information

mySCADA myPRO Manager stores credentials in cleartext, which could allow an attacker to obtain sensitive information.

Published Updated Sources: cvelistV5, icscert

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

4%

chance of exploitation in 30 days

Affects

myscada

mypro_manager

CVSS base

8.6

HIGH

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

Yes

can an attacker script all four kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

myscada

Products (1)

mypro manager

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
8.6CVSS 3.1HIGH——cvelistV5

Weakness & attack patterns

  • CWE-312

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1005Data from Local System
  • T1552.004Unsecured Credentials: Private Keys

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Indexed by

metasploit

References

3 on the record

Elsewhere on this site

  • myscadaevery CVE for this vendor
  • CWE-312other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.