Stored XSS via unsanitized Copyright Text
Published Dec 2, 2022 · Updated Jul 9, 2026
Stored XSS in Rukovoditel 3.2.1 allows remote authenticated users to execute scripts in another user's browser via Copyright Text. The Application Settings handler stores the Copyright Text value without neutralizing HTML event handlers and later renders it as active markup. An authenticated account must submit the payload and a victim must view the stored value; script execution is confined to the victim's browser context.
Summary
What happened
Stored XSS in Rukovoditel 3.2.1 allows remote authenticated users to execute scripts in another user's browser via Copyright Text. The Application Settings handler stores the Copyright Text value without neutralizing HTML event handlers and later renders it as active markup. An authenticated account must submit the payload and a victim must view the stored value; script execution is confined to the victim's browser context.
The record
- CVE
- CVE-2022-44952
- Published
- Dec 2, 2022
- Updated
- Jul 9, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 2, 2022CVE publishedPublication date reported by the CVE source.
- Jul 9, 2026Record 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
- Copyright Text stored XSS proof of conceptproof 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