CVE-2019-14273
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 assets 4.0, there is broken access control on files.
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 assets module version 4.0 contains a broken access control vulnerability that allows unauthorized access to files that should be protected or restricted. This access control failure in the file handling subsystem could allow attackers to access sensitive files without proper authentication or authorization checks.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 versionCheck the installed SilverStripe version by examining composer.json, composer.lock, or the SilverStripe admin dashboard (usually under the Help > About or similar section). Look for the core framework or assets module version.Affected if The installed SilverStripe version is 4.0.0 or lower (any version up to and including 4.0.0).
-
Locate the assets directoryFind the SilverStripe assets folder in the web root. This is typically named 'assets' and contains uploaded files. Verify this is the correct directory by checking for standard SilverStripe folder structure.Affected if An assets directory exists and contains files that should be protected or restricted from public access.
-
Check for protected asset configurationIn the SilverStripe admin panel, navigate to the Files section and check if any files or folders have been configured with protected or restricted access settings (look for File->protected or access restrictions in file/folder settings).Affected if Protected or restricted files are configured in the CMS but may be accessible due to the access control flaw.
-
Test direct access to restricted filesAttempt to access a file that should be protected by navigating directly to its URL (e.g., /assets/ProtectedFiles/filename.pdf) without logging in or authenticating. Check if the file is served without authorization checks.Affected if Files marked as protected or restricted can be downloaded or viewed directly without authentication, indicating the access control vulnerability is present.
You are affected if you are running SilverStripe version 4.0.0 or lower and have configured any files with protection or access restrictions that can be bypassed via direct URL access.
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 assets to the patched version and review file permission configurations to ensure proper access controls are enforced on all assets.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14273 — 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-14273 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