Security Research & Advisories

Reflected Cross-Site Scripting (XSS) Vulnerability in i-doit 1.14.2

Product phpList
Affected Version(s) 1.14.2 and probably prior
Tested Version(s) 1.14.2
Vendor Notification May 27, 2020
Advisory Publication May 27, 2020 [without technical details]
Vendor Fix Version 1.15
Public Disclosure August 4, 2020
Latest Modification August 4, 2020
CVE Identifier(s) CVE-2020-13825
Product Description i-doit is a web based IT documentation and CMDB. i-doit documents IT-systems and their changes, defines emergency plans, displays vital information and helps to ensure a stable and efficient IT operation.
Credits Carlos Ramírez L. Security Researcher & Penetration Tester @wizlynx group

Vulnerability Details

Reflected Cross-Site Scripting (XSS) Vulnerability
Severity: Medium CVSS Score: 5.4 CWE-ID: CWE-79 Status: Not Fixed
Vulnerability Description
The i-doit web application is affected by Reflected Cross-Site Scripting (XSS) vulnerability affecting version 1.14.2 and probably prior versions. An attacker can use the vulnerability to inject malicious JavaScript code into the application, which will execute within the browser of any user who views the relevant application content. The attacker-supplied code can perform a wide variety of actions, such as stealing victims' session tokens or login credentials, performing arbitrary actions on their behalf, and logging their keystrokes.
CVSS Base Score
Attack Vector Network Scope Changed
Attack Complexity Low Confidentiality Impact Low
Privileges Required Low Integrity Impact Low
User Interaction Required Availability Impact None


The application i-doit has one Reflected Cross-Site Scripting (XSS) vulnerability due to the lack of input validation and output encoding.


The value of the app request parameter is copied into the value of a Javascript. The payload <script>alert("XSS")</script> was submitted in the app parameter "objID", but this could be injected into any parameter shown in the URL as shown below:

This input was echoed unmodified in the application's response resulting in a Cross-Site Scripting (see request below).


The following screenshot shows the JavaScript being executed on the client side: