dbcve.org
Rtu520 FirmwareOperating system · Hitachienergy

CVE-2023-5767

MEDIUM · 6.1 CVSS v3.1 Published 2023-12-04
Fix available
A fix is available. Upgrade to after 13.4.3 or later.
See remediation →
68/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
A vulnerability exists in the webserver that affects the RTU500 series product versions listed below. A malicious actor could perform cross-site scripting on the webserver due to an RDT language file being improperly sanitized.

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

A cross-site scripting (XSS) vulnerability exists in the webserver component of ABB RTU500 series products due to improper sanitization of RDT language files. An attacker could inject malicious scripts into the language file that would then execute in the browsers of users accessing the webserver.

MitigationApply vendor-supplied patches for the RTU500 series or implement proper input validation and output encoding on the webserver to sanitize RDT language file content before rendering.

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
Rtu520 FirmwareOperating system
Affected:>= 12.0.1, <= 12.0.14>= 12.2.1, <= 12.2.11>= 12.4.1, <= 12.4.11>= 12.6.1, <= 12.6.9>= 12.7.1, <= 12.7.6>= 13.2.1, <= 13.2.6>= 13.4.1, <= 13.4.3
Rtu530 FirmwareOperating system
Affected:>= 12.0.1, <= 12.0.14>= 12.2.1, <= 12.2.11>= 12.4.1, <= 12.4.11>= 12.6.1, <= 12.6.9>= 12.7.1, <= 12.7.6>= 13.2.1, <= 13.2.6>= 13.4.1, <= 13.4.3
Rtu540 FirmwareOperating system
Affected:>= 12.0.1, <= 12.0.14>= 12.2.1, <= 12.2.11>= 12.4.1, <= 12.4.11>= 12.6.1, <= 12.6.9>= 12.7.1, <= 12.7.6>= 13.2.1, <= 13.2.6>= 13.4.1, <= 13.4.3
Rtu560 FirmwareOperating system
Affected:>= 12.0.1, <= 12.0.14>= 12.2.1, <= 12.2.11>= 12.4.1, <= 12.4.11>= 12.6.1, <= 12.6.9>= 12.7.1, <= 12.7.6>= 13.2.1, <= 13.2.6>= 13.4.1, <= 13.4.3

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 the RTU500 model
    Locate the device model identifier (Rtu520, Rtu530, Rtu540, or Rtu560) on the device label, in the web interface header, or via SNMP/system information queries.
    Affected if The model is any of Rtu520, Rtu530, Rtu540, or Rtu560.
  2. Determine the firmware version
    Access the webserver administrative interface and navigate to System > Firmware Information, or query the device via SNMP or the command-line interface using 'show firmware' or equivalent command.
    Affected if The firmware version falls within any of these ranges: 12.0.1-12.0.14, 12.2.1-12.2.11, 12.4.1-12.4.11, 12.6.1-12.6.9, 12.7.1-12.7.6, 13.2.1-13.2.6, or 13.4.1-13.4.3.
  3. Verify webserver is accessible
    Attempt to access the device webserver via HTTP or HTTPS on the configured port (typically 80 or 443, or a custom port). Confirm the login page or status page loads.
    Affected if The webserver is reachable and the device is on an affected firmware version.
  4. Inspect RDT language file configuration
    Locate RDT language files in the webserver configuration directory (commonly found under /web/lang/ or similar paths accessible via FTP/SFTP or the web interface file manager). Examine the file structure and check for any custom or user-modified XML/JSON language definition files.
    Affected if Custom or modified RDT language files exist on the device and the webserver renders these files without proper sanitization.

The environment is affected if the device is an RTU520, RTU530, RTU540, or RTU560 running firmware version 12.0.1 through 12.0.14, 12.2.1 through 12.2.11, 12.4.1 through 12.4.11, 12.6.1 through 12.6.9, 12.7.1 through 12.7.6, 13.2.1 through 13.2.6, or 13.4.1 through 13.4.3, and the webserver component is enabled.

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 a release after 13.4.3
Interim mitigation

Apply vendor-supplied patches for the RTU500 series or implement proper input validation and output encoding on the webserver to sanitize RDT language file content before rendering.

Recommended fix Moderate confidence

Contact Hitachi Energy for the specific fixed firmware release (versions beyond 12.6.9 for each affected branch)

  1. Identify the specific RTU500 series model (RTU520, RTU530, RTU540, or RTU560) in your environment
  2. Determine the current firmware version running on the affected device
  3. Contact Hitachi Energy technical support or refer to the official security advisory at publisher.hitachienergy.com to obtain the fixed firmware version
  4. Upgrade the firmware to the latest version provided by Hitachi Energy that addresses CVE-2023-5767
  5. After upgrade, verify that the webserver RDT language file is properly sanitized and no longer vulnerable to XSS
Caveat Review Hitachi Energy release notes for any functionality changes or breaking changes before upgrading production devices

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

Fix this in Rtu520 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-5767 — 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-2023-5767 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