CVE-2023-42007: IBM Sterling Control Center cross-site scripting

Published Apr 10, 2025
·
Updated

IBM Sterling Control Center 6.2.1, 6.3.1, and 6.4.0 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.

Other sources

IBM Sterling Control Center is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.

IBM

Affected Software

10 affected componentsFixes available
IBM Control Center<=6.4.0.0
IBM Control Center<=6.2.1.0
IBM Control Center<=6.3.1.0
All of the following
Any of the following
IBM Sterling Control Center=6.2.1
IBM Sterling Control Center=6.3.1
IBM Sterling Control Center=6.4.0
Any of the following
IBM AIX
IBM Linux On Ibm Z
Linux Linux kernel
Microsoft Windows

Event History

Apr 10, 2025
CVE Published
via IBM·12:00 AM
CVE Published
via MITRE·01:24 PM
Data Sourced
via MITRE·01:24 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:15 PM
DescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2023-42007?

CVE-2023-42007 has been classified as a medium severity cross-site scripting vulnerability.

2

How do I fix CVE-2023-42007?

You can fix CVE-2023-42007 by applying the appropriate patch provided by IBM for your specific version of Sterling Control Center.

3

Which versions of IBM Sterling Control Center are affected by CVE-2023-42007?

CVE-2023-42007 affects IBM Sterling Control Center versions 6.2.1, 6.3.1, and 6.4.0.

4

What are the potential impacts of CVE-2023-42007?

The potential impacts of CVE-2023-42007 include credential disclosure within a trusted session due to embedded arbitrary JavaScript code.

5

Is there a workaround for CVE-2023-42007?

Currently, no official workaround is provided for CVE-2023-42007, and the recommended action is to apply the available patches.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203