CVE-2019-12205
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 · uneditedSilverStripe through 4.3.3 has Flash Clipboard Reflected XSS.
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 confidenceSilverStripe CMS versions through 4.3.3 contain a reflected cross-site scripting (XSS) vulnerability in the Flash Clipboard functionality. The vulnerability allows attackers to inject malicious scripts through clipboard content that gets reflected without proper sanitization.
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<= 4.3.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check SilverStripe CMS versionLocate the composer.json file in your SilverStripe project root and examine the 'silverstripe/framework' or 'silverstripe/cms' version constraint. Alternatively, run 'composer show silverstripe/framework' or 'vendor/bin/silverstripe framework:info' if available.Affected if The installed version is 4.3.3 or lower (any version through 4.3.3).
-
Determine if Flash Clipboard feature is in useSearch your project codebase for references to 'Clipboard', 'flash', or 'clipboard' functionality, particularly in controllers, templates, or JavaScript files. Check if any custom code integrates with SilverStripe's built-in clipboard or flash message handling.Affected if The application uses or exposes any Flash-based clipboard functionality or reflects clipboard content in user-facing pages without sanitization.
-
Inspect Flash/Clipboard related templates and controllersReview any templates (.ss files) that handle flash messages or clipboard data. Look for instances where user-supplied data is output without proper encoding, particularly in contexts involving clipboard or flash message display.Affected if Templates or controllers reflect clipboard or flash message content without using $Upcast or proper HTML encoding.
You are affected if your SilverStripe CMS version is 4.3.3 or lower AND your application uses or exposes Flash-based clipboard functionality that reflects unsanitized user input.
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 dataUpdate SilverStripe to version 4.3.4 or later which contains the patch. As an interim measure, disable or restrict Flash-based clipboard functionality and implement Content Security Policy (CSP) headers to mitigate XSS attacks.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12205 — 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-2019-12205 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