CVE-2026-1772
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 · uneditedRTU500 web interface: An unprivileged user can read user management information. The information cannot be accessed via the RTU500 web user interface but requires further tools like browser development utilities to access them without required privileges.
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 confidenceThe RTU500 web interface has an information disclosure vulnerability where unprivileged users can access user management information through browser developer tools. The sensitive data is exposed via API endpoints that lack proper authorization checks, allowing direct object reference to user management data that should require elevated privileges.
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>= 12.7.1, <= 12.7.7>= 13.5.1, <= 13.5.4>= 13.6.1, <= 13.6.2>= 13.7.1, < 13.7.8= 13.8.1>= 12.7.1, <= 12.7.7>= 13.5.1, <= 13.5.4>= 13.6.1, <= 13.6.2>= 13.7.1, < 13.7.8= 13.8.1>= 12.7.1, <= 12.7.7>= 13.5.1, <= 13.5.4>= 13.6.1, <= 13.6.2>= 13.7.1, < 13.7.8= 13.8.1>= 12.7.1, <= 12.7.7>= 13.5.1, <= 13.5.4>= 13.6.1, <= 13.6.2>= 13.7.1, < 13.7.8= 13.8.1CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Determine the RTU firmware versionAccess the RTU web interface and navigate to System > Information or Settings > About to view the firmware version. Alternatively, check the device directly via its management interface or console.Affected if The installed firmware version falls within any of these ranges: 12.7.1 to 12.7.7, 13.5.1 to 13.5.4, 13.6.1 to 13.6.2, 13.7.1 to 13.7.7, or is exactly 13.8.1.
-
Confirm the web interface is enabledVerify that the RTU web interface HTTP/HTTPS service is running and accessible from the network. Attempt to reach the device login page via browser.Affected if The web interface is exposed and accessible to unprivileged users on the network.
-
Test unprivileged access to user management dataLog into the RTU web interface with a low-privilege or standard user account. Open browser developer tools (F12), then navigate through the interface or inspect network requests to identify any user management API endpoints. Attempt to retrieve user lists, roles, or account details.Affected if An unprivileged user can view, retrieve, or access user management information, role definitions, or account data through API calls visible in developer tools.
You are affected if your RTU520, RTU530, RTU540, or RTU560 firmware version matches one of the affected ranges AND the web interface is accessible to unprivileged users who can access user management data without elevated privileges.
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 · scoped13.7.8
Implement proper authorization checks on all API endpoints that expose user management data, ensuring unprivileged users cannot access this information regardless of how the request is made (direct UI or developer tools).
Rtu520/530/540/560 Firmware version 13.7.8 or later
- Identify the current firmware version of the affected RTU device (Rtu520, Rtu530, Rtu540, or Rtu560) by accessing the device management interface
- Determine which version branch you are currently running (12.7.x, 13.5.x, 13.6.x, or 13.7.x)
- Download the firmware version 13.7.8 or later from Hitachi Energy's official support portal at publisher.hitachienergy.com
- Review the firmware upgrade procedure in the device documentation to ensure proper backup of configuration
- Apply the firmware upgrade following the manufacturer's recommended procedure
- After upgrade, verify that the vulnerability is resolved by attempting to access user management information through browser development tools (as described in the CVE) to confirm proper privilege enforcement
- Verify that unprivileged users can no longer access user management information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1772 — 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-2026-1772 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