Browser script execution via PackageController uninstall
Published May 7, 2020 · Updated Aug 4, 2024
Cross-site scripting in UliCMS before 2020.2 allows remote attackers to execute browser script during PackageController uninstall. Public records identify the PackageController uninstall path but do not disclose the input, output sink, or missing neutralization step. A user must initiate the uninstall flow; successful execution runs in that user's browser context and can read or alter accessible application data.
Summary
What happened
Cross-site scripting in UliCMS before 2020.2 allows remote attackers to execute browser script during PackageController uninstall. Public records identify the PackageController uninstall path but do not disclose the input, output sink, or missing neutralization step. A user must initiate the uninstall flow; successful execution runs in that user's browser context and can read or alter accessible application data.
The record
- CVE
- CVE-2020-12703
- Published
- May 7, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 7, 2020CVE 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