dbcve.org
MyproApplication · Myscada

CVE-2025-23411

MEDIUM · 6.5 CVSS v3.1 Published 2025-02-13
Fix available
A fix is available. Upgrade to 1.4 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
mySCADA myPRO Manager is vulnerable to cross-site request forgery (CSRF), which could allow an attacker to obtain sensitive information. An attacker would need to trick the victim in to visiting an attacker-controlled website.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

mySCADA myPRO Manager contains a cross-site request forgery (CSRF) vulnerability. An attacker can craft malicious links on an attacker-controlled website that, when visited by an authenticated user, can cause the victim's browser to send unintended requests to the myPRO Manager application, potentially allowing unauthorized access to sensitive information.

MitigationImplement anti-CSRF tokens for all state-changing operations and configure SameSite attributes on session cookies to prevent CSRF attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MyproApplication
Affected:< 1.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed myPRO version
    Access the myPRO Manager web interface and navigate to the About/Help section, or check the version displayed in the login page or admin dashboard. Alternatively, inspect HTTP response headers or check the application installation directory for version information.
    Affected if The installed version is lower than 1.4 (e.g., 1.3.x, 1.2.x, etc.)
  2. Inspect web forms for anti-CSRF tokens
    Log into myPRO Manager, open browser developer tools (F12), go to the Network tab, and perform a state-changing action (e.g., create a user, modify settings, save configuration). Inspect the POST request payload and the original HTML form for a hidden token field or anti-CSRF parameter.
    Affected if No anti-CSRF token parameter is present in state-changing form submissions or API requests.
  3. Check session cookie SameSite attribute
    In browser developer tools, go to the Application tab and expand Cookies. Select the myPRO domain and examine the session cookie. Alternatively, capture an HTTP response using a proxy (e.g., Burp, OWASP ZAP) and inspect the Set-Cookie header for the SameSite attribute.
    Affected if The session cookie lacks the SameSite attribute, or it is set to None without Secure flag, or is missing entirely.
  4. Verify authenticated access to web interface
    Confirm that the myPRO Manager web interface is accessible and that user authentication is required to access sensitive functions. Attempt to access protected endpoints without authentication or check if sessions are required.
    Affected if The web interface is accessible to unauthenticated users, or authenticated sessions can be hijacked via CSRF because no token validation occurs.

A user is affected if their myPRO Manager version is below 1.4 AND the application lacks anti-CSRF tokens in state-changing operations AND session cookies do not have proper SameSite attributes configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.4 or later
Fixed in 1.4
Interim mitigation

Implement anti-CSRF tokens for all state-changing operations and configure SameSite attributes on session cookies to prevent CSRF attacks.

Recommended fix Moderate confidence

1.4

  1. 1. Download the latest mySCADA myPRO version 1.4 from the official vendor website (www.myscada.org)
  2. 2. Back up the existing myPRO configuration and project files before upgrading
  3. 3. Stop the myPRO Manager service if it is currently running
  4. 4. Install version 1.4 following the vendor's installation instructions
  5. 5. Restore the backed-up configuration and project files to the new installation
  6. 6. Start the myPRO Manager service and verify the application is functioning correctly
  7. 7. Verify that the CSRF protection mechanisms are properly functioning in the upgraded version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mypro Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,768.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-23411 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-23411 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data