CentOS Web Panel 0.9.8.1081 - Stored Cross-Site Scripting (XSS)

vendor:

CentOS Web Panel

by:

Dinesh Mohanty

8,8

CVSS

HIGH

Stored Cross Site Scripting (Stored XSS)

CWE

Product Name: CentOS Web Panel

Affected Version From: v0.9.8.1081

Affected Version To: v0.9.8.1081

Patch Exists: YES

Related CWE: N/A

CPE: a:centos_webpanel:centos_webpanel:0.9.8.1081

Metasploit: N/A

Other Scripts: N/A

Tags: N/A

CVSS Metrics: N/A

Nuclei References: N/A

Nuclei Metadata: N/A

Platforms Tested: CentOS 7 and 8

2021

CentOS Web Panel 0.9.8.1081 – Stored Cross-Site Scripting (XSS)

Multiple Stored Cross Site Scripting (Stored XSS) Vulnerability is found in the Short Name, Ip Origin, Key Code, Format Request and Owner fields within the admin api page of module of CentOS/ Control WebPanel when user tries to create a new API. This is because the application does not properly sanitize users input.

Mitigation:

Input validation and sanitization should be done to prevent XSS attacks.

Source

Exploit-DB raw data:

# Exploit Title: CentOS Web Panel 0.9.8.1081 - Stored Cross-Site Scripting (XSS)
# Date: 13/08/2021
# Exploit Author: Dinesh Mohanty
# Vendor Homepage: http://centos-webpanel.com
# Software Link: http://centos-webpanel.com
# Version: v0.9.8.1081
# Tested on: CentOS 7 and 8

# Description:
Multiple Stored Cross Site Scripting (Stored XSS) Vulnerability is found in the Short Name, Ip Origin, Key Code, Format Request and Owner fields within the admin api page of module of CentOS/ Control WebPanel when user tries to create a new API. This is because the application does not properly sanitize users input.


# Steps to Reproduce:
1. Login into the CentOS Web Panel using admin credential.
2. From Navigation Click on "API Manager" -> then Click on "Allow New API Access"
3. In the above given fields give payload as: <img src=x onerror=alert(1)> and provide other details and click on "Create"
4. Now one can see that the XSS Payload executed.

#Vendor Notification
18th Aug 2021 - Vendor has been notified
18th Aug 2021 - Vendor confirmed the issue and fixed for next version