Stored script execution via unencoded user fields
Published Jun 24, 2020 · Updated Aug 4, 2024
Stored XSS in Navigate CMS 2.9 r1433 allows remote attackers to execute attacker-controlled script through crafted user profile fields. The Users/Edit page fails to HTML-encode the E-Mail field, while the Users view renders stored User and E-Mail values without sufficient encoding. The injection route's access requirements are not published; exploitation requires a user to view or edit the affected record in a browser.
Summary
What happened
Stored XSS in Navigate CMS 2.9 r1433 allows remote attackers to execute attacker-controlled script through crafted user profile fields. The Users/Edit page fails to HTML-encode the E-Mail field, while the Users view renders stored User and E-Mail values without sufficient encoding. The injection route's access requirements are not published; exploitation requires a user to view or edit the affected record in a browser.
The record
- CVE
- CVE-2020-14018
- Published
- Jun 24, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 24, 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
- Navigate CMS stored XSS demonstrationproof of concept · demonstrated
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