dbcve.org
460 Series FirmwareOperating system · Rtautomation

CVE-2023-4523

MEDIUM · 6.1 CVSS v3.1 Published 2023-09-27
Fix available
A fix is available. Upgrade to 8.9.8 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
Real Time Automation 460 Series products with versions prior to v8.9.8 are vulnerable to cross-site scripting, which could allow an attacker to run any JavaScript reference from the URL string. If this were to occur, the gateway's HTTP interface would redirect to the main page, which is index.htm.

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 · high confidence

The RTA 460 Series gateway web interface contains a reflected cross-site scripting vulnerability in versions prior to v8.9.8. User-supplied JavaScript can be injected via the URL string and executed in the context of the user's browser, leading to potential session hijacking or credential theft. The vulnerable endpoint reflects the unsanitized input back to the user.

MitigationUpgrade the RTA 460 Series firmware to version v8.9.8 or later to obtain the vendor fix. If immediate patching is not possible, restrict network access to the device's HTTP management interface and monitor for suspicious URL patterns.

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
460 Series FirmwareOperating system
Affected:< 8.9.8

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 device model
    Access the device's web interface or check the device label/metadata to confirm it is an RTA 460 Series gateway. The device typically displays its model name on the login page or in the system information section.
    Affected if The device is not an RTA 460 Series gateway - this CVE does not apply to other models.
  2. Determine the installed firmware version
    Log into the web interface and navigate to System > Status, System > About, or a similar information page. The firmware version is typically displayed as a version number (e.g., v8.9.7, v8.9.6). Alternatively, check the boot log or system diagnostics if CLI access is available.
    Affected if The firmware version is displayed as lower than v8.9.8 (for example, v8.9.7, v8.9.5, or earlier). Versions prior to 8.9.8 are affected.
  3. Verify the web interface is enabled
    Confirm that the HTTP or HTTPS web management interface is active by attempting to access the device's IP address in a browser. The login page should load.
    Affected if The web interface is accessible and running. The reflected XSS only executes when a user interacts with the vulnerable endpoint via the browser.
  4. Check for the vulnerable URL reflection behavior
    Inspect URLs used in the web interface, particularly any parameters that might reflect back in the response (such as in error messages, navigation state, or search fields). Look for unsanitized reflection of input in the HTML source.
    Affected if The web interface reflects URL parameters or path segments back into the rendered page without proper sanitization. This confirms the XSS vulnerability is present and exploitable.

You are affected if the device is an RTA 460 Series gateway running firmware version lower than v8.9.8 and the web interface is accessible, as the reflected XSS vulnerability exists in versions prior to the fix.

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 8.9.8 or later
Fixed in 8.9.8
Interim mitigation

Upgrade the RTA 460 Series firmware to version v8.9.8 or later to obtain the vendor fix. If immediate patching is not possible, restrict network access to the device's HTTP management interface and monitor for suspicious URL patterns.

Recommended fix High confidence

460 Series Firmware v8.9.8 or later

  1. Identify the current firmware version of the Real Time Automation 460 Series device
  2. Download firmware version 8.9.8 or later from the official Real Time Automation vendor
  3. Access the device's web interface or console to initiate the firmware upgrade process
  4. Upload and apply the new firmware version following the vendor's documented upgrade procedure
  5. After upgrade, verify the device is running firmware version 8.9.8 or later
  6. Confirm the XSS vulnerability is remediated by testing that JavaScript in URL parameters is no longer executed

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

Fix this in 460 Series Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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