CVE-2023-47714
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 · uneditedIBM Sterling File Gateway 6.0.0.0 through 6.0.3.9, 6.1.0.0 through 6.1.2.3, and 6.2.0.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. IBM X-Force ID: 271531.
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 confidenceIBM Sterling File Gateway contains a stored cross-site scripting (XSS) vulnerability in its Web UI. An authenticated attacker can inject malicious JavaScript code into web interface fields that executes in the browsers of other users viewing the same content, potentially allowing session hijacking or credential theft within a trusted session.
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>= 6.0.0.0, <= 6.0.3.9>= 6.1.0.0, <= 6.1.2.3= 6.2.0.0CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify IBM Sterling File Gateway installationLocate the installation directory or check system inventory for IBM Sterling File Gateway. Common paths include /opt/ibm or installation-specific directories. Use 'ls' or file search commands to find Sterling File Gateway binaries or configuration files.Affected if IBM Sterling File Gateway is installed on the system
-
Determine installed versionCheck the product version by inspecting version files, startup scripts, or the admin console. Look for a version file in the installation directory or use the command 'productVersion' or 'version' if available in the bin folder. The version typically appears in the format such as 6.0.x.x, 6.1.x.x, or 6.2.0.0.Affected if The installed version falls within 6.0.0.0-6.0.3.9, 6.1.0.0-6.1.2.3, or equals 6.2.0.0
-
Verify Web UI is enabledCheck if the Web UI component is configured and accessible. Examine the configuration files (such as server.xml, web.xml, or similar) in the installation directory for the Web UI module status. Confirm the HTTP/HTTPS ports for the Web UI are active and listening.Affected if The Web UI is enabled and accessible to users
If IBM Sterling File Gateway is installed with a version in the affected ranges (6.0.0.0-6.0.3.9, 6.1.0.0-6.1.2.3, or 6.2.0.0) and the Web UI is enabled, the environment is vulnerable to stored XSS attacks.
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.
From vendor dataApply IBM's published security patches for the affected versions (6.0.0.0-6.0.3.9, 6.1.0.0-6.1.2.3, 6.2.0.0) or upgrade to a patched release. Implement input validation and output encoding on all user-supplied data in the Web UI as an interim control.
- Consultation3.0 h
- Implementation4.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 $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47714 — 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-2023-47714 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