CVE-2023-30963
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 · uneditedA security defect was discovered in Foundry Frontend which enabled users to perform Stored XSS attacks in Slate if Foundry's CSP were to be bypassed. This defect was resolved with the release of Foundry Frontend 6.229.0. The service was rolled out to all affected Foundry instances. No further intervention is required.
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 confidenceA Stored XSS vulnerability existed in Foundry Frontend's Slate component that could be exploited if Foundry's Content Security Policy (CSP) were bypassed. The flaw was remediated in Foundry Frontend version 6.229.0.
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.229.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 Foundry Frontend versionAccess the Foundry administration console or check the frontend deployment metadata to retrieve the currently deployed version number. This is typically visible in the 'About' section or deployment logs.Affected if The displayed version is below 6.229.0 (e.g., 6.228.x, 6.227.x, etc.)
-
Confirm Slate component is activeCheck if the Slate rich-text editor component is enabled in the Foundry platform configuration. This can be verified through the platform admin settings or by inspecting which components are loaded in the Foundry UI.Affected if Slate component is actively used in the environment and the frontend version is below 6.229.0
-
Verify CSP configuration statusReview Foundry's Content Security Policy settings in the admin security console. Determine whether the default CSP protections are in place or if any custom rules exist that may weaken the policy.Affected if CSP has been weakened, bypassed, or custom rules allow inline scripts, and the frontend version is below 6.229.0
You are affected if Foundry Frontend is deployed with a version below 6.229.0 AND the Slate component is in use AND the CSP has been weakened or bypassed.
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 · scoped6.229.0
No further action required as version 6.229.0 containing the fix has already been rolled out to all affected instances. Verify deployed version if concerned.
Foundry Frontend 6.229.0
- This fix has already been automatically deployed by Palantir to all affected Foundry instances.
- No further intervention is required per the vendor's advisory.
- If you have not received the update or have concerns, contact Palantir Foundry support for verification.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30963 — 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-30963 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