CVE-2019-14272
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 · uneditedIn SilverStripe asset-admin 4.0, there is XSS in file titles managed through the CMS.
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 confidenceStored XSS vulnerability in SilverStripe CMS 4.0's asset-admin module allows injection of malicious scripts through file titles. The vulnerability is exploitable when users view or interact with files in the CMS interface where unsanitized file titles are rendered.
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.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 SilverStripe CMS versionLocate the SilverStripe version file or check the composer.json in the web root for the 'silverstripe/framework' or 'silverstripe/cms' package versionAffected if The installed version is 4.0.0 or lower (< 4.0.1)
-
Confirm asset-admin module presenceCheck if the asset-admin module exists in vendor/silverstripe/assets-admin or is part of the installed packages (this is included by default in SilverStripe CMS 4.0)Affected if The asset-admin module is installed as part of the SilverStripe 4.0.x installation
-
Check if file upload functionality is accessibleVerify that users can access the Assets section in the CMS admin interface and upload filesAffected if The Assets/File section in the CMS admin is accessible to users who can set file titles
-
Review file title rendering in CMSInspect the CMS interface (Assets section) to see if file titles are displayed without visible encoding when files are viewed in the file managerAffected if File titles can contain arbitrary characters that render as-is in the CMS interface (symptom of missing sanitization)
-
Verify patch statusIf using a 4.0.x version, check if vendor/silverstripe/assets-admin/src/Controller/AssetAdmin.js or related template files contain sanitization calls for file titles (such as Encode::xmlEncode or equivalent)Affected if No output encoding is applied to file titles in the asset-admin templates or JavaScript
You are affected if SilverStripe CMS version 4.0.0 or lower is installed and the asset-admin module is active, allowing malicious script injection through unsanitized file titles displayed in the CMS.
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 dataUpgrade SilverStripe to version 4.0.1 or later which contains the security patch, or implement output encoding/sanitization for file titles in the asset-admin interface.
- 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-14272 — 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-14272 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