CVE-2020-36954
Stored XSS in Xeroneit LMS 3.1 Book Category Allows Script Injection
Publication date: 2026-01-26
Last updated on: 2026-01-26
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| xeroneit | library_management_system | to 3.1 (exc) |
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
Can you explain this vulnerability to me?
CVE-2020-36954 is a stored cross-site scripting (XSS) vulnerability in the Xeroneit Library Management System version 3.1. It occurs in the 'Add Book Category' feature, where an attacker with administrator privileges can inject malicious JavaScript code into the Category Name input field. This malicious script is stored and executed whenever the affected page is loaded, allowing arbitrary JavaScript code execution in the context of the application. [2, 4]
How can this vulnerability impact me? :
This vulnerability can allow an attacker with admin privileges to execute arbitrary JavaScript code within the application. This can lead to unauthorized actions such as stealing session cookies, defacing the website, redirecting users to malicious sites, or performing actions on behalf of other users. Although the impact on confidentiality, integrity, and availability is rated low to medium, it still poses a security risk by enabling script execution in users' browsers. [2, 4]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by attempting to inject a test payload into the 'Category Name' field in the 'Add Book Category' feature while logged in as an administrator. For example, inserting a payload like `"><img src onerror=alert(1)>` and then observing if the script executes when the page loads. This confirms the presence of stored XSS. The detection involves logging into the application as an admin, navigating to the Book Category section, clicking Add, and entering the payload. There are no specific network commands provided, but manual testing through the web interface is recommended. [4]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting administrator access to trusted users only, avoiding input of untrusted data into the Category Name field, and applying input validation and output encoding to neutralize scripts. If a patch or update is available from the vendor, apply it promptly. Additionally, monitoring and sanitizing inputs in the Book Category feature can help prevent exploitation. [2, 4]