CriticalPublic exploit

Cleartext Credential Storage in mySCADA myPRO Manager

IdentifiersCVE-2025-22896CWE-312· Cleartext Storage of Sensitive…

mySCADA myPRO Manager stores credentials in cleartext, making them accessible to anyone with access to the storage location. This vulnerability exposes sensitive authentication information, as credentials are not protected by encryption or hashing mechanisms.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An attacker with access to the system or storage medium can easily retrieve credentials, potentially leading to unauthorized access to the mySCADA myPRO Manager and associated systems. This could result in compromise of industrial control systems managed by myPRO Manager.

Mitigation

If you can’t patch tonight, do this now.

Restrict access to the storage location where credentials are kept. Use file system permissions and network segmentation to limit exposure until a patch is applied.

Remediation

Patch, then assume compromise.

Update mySCADA myPRO Manager to a version that securely stores credentials using strong cryptographic methods. Ensure that all plaintext credentials are purged from the system after upgrading.

PUBLIC EXPLOITS

Exploits

1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.

VALID 1 / 1 TOTALView more in app

mypro_mgr_creds.rbMaturityWeaponizedFrameworkmetasploitVerified exploit

This repository contains a single Metasploit auxiliary module targeting mySCADA myPRO Manager (<= v1.3) for Windows. The module exploits two vulnerabilities (CVE-2025-24865 and CVE-2025-22896) that allow unauthenticated attackers to harvest SMTP mail server credentials from the target system. The exploit works by sending a POST request with the command 'getSettings' to the '/get' endpoint of the web interface, which returns the SMTP configuration in cleartext due to broken authentication. The module also includes a check method that retrieves the application version from the '/assets/index-DBkpc6FO.js' endpoint to determine if the target is vulnerable. The exploit is operational and provides cleartext credentials if successful. The code is written in Ruby and is structured as a standard Metasploit module.

Disclosed Feb 13, 2025rubynetwork

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

MyscadaMyproapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

No public activity tracked yet. Mallory keeps watching.

0 SOURCESView more in app

No public activity observed for this vulnerability.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity