Stored XSS via unsanitized Scan Engine name
Published Mar 24, 2022 · Updated Aug 4, 2024
Stored XSS in Yogesh Ojha reNgine 1.0 allows remote authenticated users to execute JavaScript through a crafted Scan Engine name. The deletion confirmation modal inserts the stored engine name into its prompt without sanitization, so an embedded event handler runs when the delete control is opened. Exploitation requires an account that can add a Scan Engine and user interaction with its deletion control, and the script runs in the victim's browser context.
Summary
What happened
Stored XSS in Yogesh Ojha reNgine 1.0 allows remote authenticated users to execute JavaScript through a crafted Scan Engine name. The deletion confirmation modal inserts the stored engine name into its prompt without sanitization, so an embedded event handler runs when the delete control is opened. Exploitation requires an account that can add a Scan Engine and user interaction with its deletion control, and the script runs in the victim's browser context.
The record
- CVE
- CVE-2021-39491
- Published
- Mar 24, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 24, 2022CVE 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Scan Engine name stored-XSS reproductionproof 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