CVE-2019-12437
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 through 4.3.3, the previous fix for SS-2018-007 does not completely mitigate the risk of CSRF in GraphQL mutations,
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 confidenceThis is a CSRF (Cross-Site Request Forgery) vulnerability in SilverStripe's GraphQL module. The previous fix for SS-2018-007 incompletely addressed CSRF protection for GraphQL mutations, allowing attackers to potentially execute unauthorized GraphQL operations by tricking authenticated users into visiting malicious pages.
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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 if GraphQL module is installedExamine your composer.json for 'silverstripe/graphql' in the require section, or check the vendor directory for silverstripe/graphql presenceAffected if GraphQL module is installed and the site uses GraphQL functionality
-
Determine SilverStripe core versionRun 'composer show silverstripe/framework' or check the silverstripe.framework composer package version in your vendor directoryAffected if SilverStripe version is 4.3.3 or lower (any version <= 4.3.3)
-
Verify GraphQL endpoint is exposedCheck your site configuration (typically mysite/_config.php or app/_config.php) for GraphQL::enable() calls, and test accessing /graphql/v1 endpointAffected if GraphQL endpoint is accessible and the module is enabled
-
Confirm CSRF protection status in GraphQLInspect the GraphQL mutations in your vendor/silverstripe/graphql/src directory, specifically looking for CSRFTokenProvider validation in mutation classes or the schema configurationAffected if No CSRF token validation is enforced on GraphQL mutation operations
You are affected if SilverStripe version is 4.3.3 or lower AND the GraphQL module is enabled with mutations exposed, as the incomplete CSRF fix allows unauthorized mutation execution.
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 the latest version beyond 4.3.3, which contains the complete fix for this CSRF bypass in GraphQL mutations. If immediate upgrading is not possible, consider disabling the GraphQL module if not required.
- 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-12437 — 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-12437 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