CVE-2019-19712
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 · uneditedContao 4.0 through 4.8.5 has Insecure Permissions. Back end users can manipulate the details view URL to show pages and articles that have not been enabled for them.
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 confidenceContao CMS versions 4.0-4.8.5 contain an insecure permission flaw in the backend where users can manipulate the details view URL parameters to access pages and articles they are not authorized to view. This is an authorization bypass through URL manipulation.
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.4.0, <= 4.4.45>= 4.8, <= 4.8.5= 4.0= 4.1= 4.2= 4.3= 4.5= 4.6= 4.7CVSS 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.
-
Determine installed Contao versionCheck the composer.json file in the Contao root directory for the contao/contao package version, or access the backend and navigate to System > Settings or System Information to view the version number.Affected if The installed version is 4.0, 4.1, 4.2, 4.3, 4.4.0-4.4.45, 4.5, 4.6, 4.7, or 4.8.0-4.8.5.
-
Confirm backend access is availableVerify that the Contao backend (/contao or /admin path) is accessible and that user accounts exist with backend login credentials.Affected if The backend is publicly or internally accessible with valid user credentials.
-
Identify if details view feature existsLocate the details view functionality in the backend - this typically appears when viewing a list of pages, articles, or content elements where a details/ preview link is provided.Affected if The backend contains list views with details view links that expose record IDs in the URL.
-
Check URL parameter handling for authorization bypassAs a low-privilege backend user, access a details view URL for a record you are not authorized to view by manipulating the ID or item parameter in the URL, such as changing the ID to reference a protected page or article.Affected if The details view loads content for records outside the user's authorized scope, indicating the authorization bypass is present.
A user is affected if they run Contao version 4.0 through 4.8.5 and the backend is accessible to users who should not have full visibility of all pages or articles.
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 Contao to version 4.8.6 or later which contains the security fix for proper permission validation on the details view.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19712 — 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-19712 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