CVE-2024-47117
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 Carbon Design System (Carbon Charts 0.4.0 through 1.13.16) is vulnerable to cross-site scripting. This vulnerability allows an authenticated user to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.
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 confidenceIBM Carbon Charts versions 0.4.0 through 1.13.16 contain a stored XSS vulnerability where an authenticated user can inject arbitrary JavaScript code into chart data or labels. When other users view the affected charts, the malicious script executes within their trusted session context, potentially exposing credentials or session tokens.
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>= 0.4.0, < 1.13.17CVSS 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.
-
Locate IBM Carbon Charts versionSearch for 'ibm-carbon-charts' or '@carbon/charts' in your package.json, package-lock.json, yarn.lock, or npm list output. Also check any bundler dependency trees.Affected if The reported version is >= 0.4.0 and < 1.13.17
-
Identify chart data sourcesReview the codebase for calls to chart rendering functions (such as CoreChart, AngularChart, ReactChart, VueChart, or SvelteChart) and trace where the data and labels parameters come from.Affected if User-supplied input (from HTTP requests, databases, files, or APIs) flows directly into chart data or label properties without sanitization or encoding
-
Check for output encoding on chart inputsSearch for uses of chart rendering methods and verify whether any encoding functions (such as escaping HTML entities) are applied to data and label values before they are passed to the chart component.Affected if User-provided values are passed to chart data or labels without any form of output encoding or sanitization
-
Verify authentication and chart creation accessDetermine whether the application allows authenticated users to create or modify charts, since the vulnerability requires an authenticated user to inject the malicious payload.Affected if The application permits authenticated users to create, update, or provide chart configuration data
You are affected if your IBM Carbon Charts version is 0.4.0 through 1.13.16 and your application passes unsanitized user input directly to chart data or label properties.
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 · scoped1.13.17
Upgrade IBM Carbon Charts to a version beyond 1.13.16 that includes the XSS fix, and implement output encoding on all user-supplied data before rendering in charts.
1.13.17
- Upgrade IBM Carbon Charts to version 1.13.17 or later
- Verify the upgrade resolves the XSS vulnerability by testing with the previously vulnerable vector
- Confirm application functionality remains intact after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47117 — 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-2024-47117 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