Authenticated privilege escalation via Velocity configuration injection
Published Aug 18, 2021 · Updated Aug 4, 2024
Incorrect access control in dotCMS before 5.1 allows remote authenticated users to gain privileges through crafted Velocity templates. VTL file handling accepts injected client configurations, while the upstream issue discloses no affected class, method, or missing validation check. A low-privilege account is required, and successful exploitation elevates that account within the dotCMS application.
Summary
What happened
Incorrect access control in dotCMS before 5.1 allows remote authenticated users to gain privileges through crafted Velocity templates. VTL file handling accepts injected client configurations, while the upstream issue discloses no affected class, method, or missing validation check. A low-privilege account is required, and successful exploitation elevates that account within the dotCMS application.
The record
- CVE
- CVE-2020-18875
- Published
- Aug 18, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-74, T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 18, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo