CVE-2019-12872
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 · unediteddotCMS before 5.1.6 is vulnerable to a SQL injection that can be exploited by an attacker of the role Publisher via view_unpushed_bundles.jsp.
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 confidenceSQL injection vulnerability in dotCMS view_unpushed_bundles.jsp allows attackers with the Publisher role to execute arbitrary SQL queries via unsanitized input, potentially leading to unauthorized data access or manipulation of the database.
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< 5.1.6CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/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 installed dotCMS versionLocate the dotCMS installation directory and find the version file or check the admin dashboard for the version information. Common locations include version.properties or the admin interface.Affected if The installed version is lower than 5.1.6 (e.g., 5.1.5, 5.1.0, etc.)
-
Identify users with Publisher roleAccess the dotCMS admin panel and navigate to the Roles or User management section. Look for users or groups assigned the Publisher role.Affected if Any user account is assigned the Publisher role, granting access to the vulnerable functionality
-
Locate view_unpushed_bundles.jspSearch for the file view_unpushed_bundles.jsp in the dotCMS web application directory, typically found under the admin or backend portal paths.Affected if The file exists in the deployment and is accessible via the web interface
-
Verify Publisher role access to vulnerable endpointIf the Publisher role exists and the JSP file is present, attempt to access the view_unpushed_bundles endpoint using an account with Publisher privileges to confirm the attack surface exists.Affected if A user with Publisher role can access the view_unpushed_bundles functionality without additional authentication barriers
You are affected if your dotCMS version is below 5.1.6 and you have users with the Publisher role who can access view_unpushed_bundles.jsp, allowing them to inject arbitrary SQL through unsanitized input parameters.
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 data5.1.6
Upgrade dotCMS to version 5.1.6 or later. If immediate upgrade is not possible, implement input validation and parameterized queries in view_unpushed_bundles.jsp to mitigate the SQL injection vector.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12872 — 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-12872 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