CVE-2023-53898
BaseFortify
Publication date: 2025-12-16
Last updated on: 2025-12-27
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| rukovoditel | rukovoditel | 3.4.1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by inspecting the application's copyright text configuration for injected iframe or script payloads. Since it is a stored XSS affecting authenticated users, you can check the stored configuration fields for suspicious script tags or iframe elements. Commands or tools to detect this might include using web application scanners that detect stored XSS or manually querying the configuration database or files for suspicious content. Specific commands are not provided in the resources. [1]
Can you explain this vulnerability to me?
This vulnerability in Rukovoditel 3.4.1 is a stored cross-site scripting (XSS) issue that allows authenticated attackers to inject malicious scripts. Specifically, attackers can insert iframe and script payloads into the application's copyright text, which then execute arbitrary JavaScript in the browsers of users who view that text.
How can this vulnerability impact me? :
The vulnerability can impact you by allowing attackers to execute arbitrary JavaScript in the browsers of authenticated users. This can lead to unauthorized actions performed on behalf of users, theft of sensitive information such as session tokens, or other malicious activities that compromise user security and application integrity.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting or sanitizing user input in the application's configuration fields, especially the copyright text, to prevent injection of scripts or iframes. Applying patches or updates from the vendor that address this vulnerability is recommended once available. Additionally, limiting privileges of authenticated users to reduce the risk of exploitation and educating users about the risk of interacting with untrusted content can help mitigate impact. [1]