CVE-2019-12203
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 allows session fixation in the "change password" form.
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 confidenceSilverStripe CMS through version 4.3.3 contains a session fixation vulnerability in the change password form. When a user changes their password, the application fails to regenerate the session ID, allowing an attacker who can set or predict the session ID to potentially hijack the user's authenticated session after the password change completes.
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
- Physical
- Complexity
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/AC:H/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.
-
Identify installed SilverStripe versionLocate the SilverStripe framework version file or check composer.json for the silverstripe/framework package versionAffected if The installed version is 4.3.3 or any earlier version (4.x branch)
-
Confirm password change form is accessibleVerify the change password functionality is enabled in the CMS or frontend - typically at /admin/security or /Security/ChangePasswordAffected if The password change form is available to authenticated users without additional access restrictions
-
Test session ID behavior during password changeLog in with a known session ID, change the password using the form, then check if the session ID changes after the password change completesAffected if The session ID remains the same before and after the password change (session fixation vulnerability present)
-
Review authentication-related session handlingInspect the code handling password change (typically in ChangePasswordForm.php or equivalent) for session_regenerate_id() calls after successful password updateAffected if The code lacks session regeneration logic following a successful password change
A user is affected if running SilverStripe version 4.3.3 or earlier AND the password change functionality is accessible to authenticated users without proper session regeneration occurring after the password is changed.
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.3.4 or later which contains the session regeneration fix. Alternatively, ensure all authentication-related actions (including password changes) properly invalidate and regenerate session IDs.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12203 — 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-12203 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