CVE-2025-39201
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 · uneditedA vulnerability exists in MicroSCADA X SYS600 product. If exploited this could allow a local unauthenticated attacker to tamper a system file, making denial of Notify service.
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 confidenceA local unauthenticated attacker can tamper with a system file in MicroSCADA X SYS600, causing denial of the Notify service. This file tampering vulnerability allows privilege escalation through file system manipulation, resulting in service disruption.
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>= 10.0, < 10.7CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed versionCheck the version of Hitachi Energy MicroSCADA X SYS600 installed in your environment using system inventory tools or product-specific queriesAffected if The installed version falls within the range of 10.0 to less than 10.7
-
Locate Notify service configuration filesIdentify the configuration files associated with the Notify service in the MicroSCADA X SYS600 installation directoryAffected if The Notify service configuration files exist and are accessible on the system
-
Verify file permissions on system filesReview file permissions on system files and Notify service configuration files to determine if unauthorized modification is possibleAffected if File permissions allow modification by unauthenticated or low-privilege users
-
Check for unauthorized file modificationsCompare current file timestamps and checksums of system files against known good baselinesAffected if System files have been modified without authorized changes
-
Confirm Notify service statusVerify if the Notify service is running and responsive in your environmentAffected if The Notify service is experiencing disruption or denial
Your environment is affected if MicroSCADA X SYS600 version 10.0 through 10.6.x is installed and the Notify service configuration files have insufficient access controls allowing unauthenticated tampering.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.7
Restrict file permissions on system files to prevent unauthorized tampering by unauthenticated users, and implement proper access controls on the Notify service configuration files.
10.7
- Verify current MicroSCADA X SYS600 version by checking the installed software version
- Schedule a maintenance window for the upgrade procedure
- Backup current system configuration and data according to site-specific backup procedures
- Download MicroSCADA X SYS600 version 10.7 from Hitachi Energy's official support portal (publisher.hitachienergy.com)
- Install version 10.7 following the product's standard upgrade documentation
- Verify the Notify service is running correctly after upgrade
- Validate that default file permissions are correctly set post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-39201 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-39201 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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