Authenticated stored XSS via unsanitized nickname
Published Sep 15, 2021 · Updated Aug 4, 2024
Stored XSS in JFinal CMS 4.7.1 and earlier allows remote authenticated users to execute script via a crafted profile nickname. The profile update path stores the Nickname parameter, and profile.html renders it without neutralizing attacker-controlled HTML or script. Low-privileged account access and a later victim visit to the affected profile are required, bounding impact to browser-session data and actions.
Summary
What happened
Stored XSS in JFinal CMS 4.7.1 and earlier allows remote authenticated users to execute script via a crafted profile nickname. The profile update path stores the Nickname parameter, and profile.html renders it without neutralizing attacker-controlled HTML or script. Low-privileged account access and a later victim visit to the affected profile are required, bounding impact to browser-session data and actions.
The record
- CVE
- CVE-2020-19148
- Published
- Sep 15, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 15, 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
- Seebug SSVID-97879 exploit referenceproof of concept · unverified
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