Stored XSS viva .svg file upload in GitHub repository causefx/organizr prior to 2.1.1810. This allows attackers to execute malicious scripts in the user's browser and it can lead to session hijacking, sensitive data exposure, and worse.

**Description**

The application allows .svg files to upload which leads to stored XSS

**Proof of Concept**

1.Download the payload from this link:- https://drive.google.com/file/d/1c1BP5bxXBxtwLfRJTrEPgMWK1yVFDF2R/view?usp=sharing

2.Login to the application with Co-admin account and go to "Settings" -> "Image Manager" and upload the downloaded "XSS.svg" payload.

3.Then login with admin account and go to "Settings" -> "Image Manager" and select the "XSS.svg" and open it on a new tab or open the uploaded location you will see that XSS will trigger and this can lead to the admin account takeover.

**PoC video:**

    https://drive.google.com/file/d/1jdjUHuQPG0xVR3pImcg3vT4cuxhIEuBi/view?usp=sharing
    

**Impact**

This allows attackers to execute malicious scripts in the user's browser and it can lead to session hijacking, sensitive data exposure, and worse.

CVE-2022-1345: Stored XSS viva .svg file upload in organizr

Stored XSS in the "Username" & "Email" input fields leads to account takeover of Admin & Co-admin users in GitHub repository causefx/organizr prior to 2.1.1810. Account takeover and privilege escalation

@@ -1895,7 +1895,7 @@ public function uploadImage() $tempFile = $\_FILES\['file'\]\['tmp\_name'\]; $targetPath = $this\->root . DIRECTORY\_SEPARATOR . 'data' . DIRECTORY\_SEPARATOR . 'userTabs' . DIRECTORY\_SEPARATOR; $this\->makeDir($targetPath); $targetFile = $targetPath . $\_FILES\['file'\]\['name'\]; $targetFile = $targetPath . $this\->sanitizeUserString($\_FILES\['file'\]\['name'\]); $this\->setAPIResponse(null, pathinfo($\_FILES\['file'\]\['name'\], PATHINFO\_BASENAME) . ' has been uploaded', null); return move\_uploaded\_file($tempFile, $targetFile); } @@ -4873,7 +4873,7 @@ public function addTab($array) $array\['type'\] = ($array\['type'\]) ?? 1; $array\['order'\] = ($array\['order'\]) ?? $this\->getNextTabOrder() + 1; if (array\_key\_exists('name', $array)) { $array\['name'\] = htmlspecialchars($array\['name'\]); $array\['name'\] = $this\->sanitizeUserString($array\['name'\]); if ($this\->isTabNameTaken($array\['name'\])) { $this\->setAPIResponse('error', 'Tab name: ' . $array\['name'\] . ' is already taken', 409); return false; @@ -4923,7 +4923,7 @@ public function updateTab($id, $array) return false; } if (array\_key\_exists('name', $array)) { $array\['name'\] = htmlspecialchars($array\['name'\]); $array\['name'\] = $this\->sanitizeUserString($array\['name'\]); if ($this\->isTabNameTaken($array\['name'\], $id)) { $this\->setAPIResponse('error', 'Tab name: ' . $array\['name'\] . ' is already taken', 409); return false; @@ -4995,6 +4995,7 @@ public function addCategory($array) $array\['order'\] = ($array\['order'\]) ?? $this\->getNextCategoryOrder() + 1; $array\['category\_id'\] = ($array\['category\_id'\]) ?? $this\->getNextCategoryId() + 1; if (array\_key\_exists('category', $array)) { $array\['category'\] = $this\->sanitizeUserString($array\['category'\]); if ($this\->isCategoryNameTaken($array\['category'\])) { $this\->setAPIResponse('error', 'Category name: ' . $array\['category'\] . ' is already taken', 409); return false; @@ -5005,6 +5006,9 @@ public function addCategory($array) } if (!array\_key\_exists('image', $array)) { $this\->setAPIResponse('error', 'Category image was not supplied', 422); return false; } else { $array\['image'\] = $this\->sanitizeUserString($array\['image'\]); } $response = \[ array( @@ -5039,11 +5043,15 @@ public function updateCategory($id, $array) return false; } if (array\_key\_exists('category', $array)) { $array\['category'\] = $this\->sanitizeUserString($array\['category'\]); if ($this\->isCategoryNameTaken($array\['category'\], $id)) { $this\->setAPIResponse('error', 'Category name: ' . $array\['category'\] . ' is already taken', 409); return false; } } if (array\_key\_exists('image', $array)) { $array\['image'\] = $this\->sanitizeUserString($array\['image'\]); } if (array\_key\_exists('default', $array)) { if ($array\['default'\]) { $this\->clearCategoryDefault(); @@ -6184,6 +6192,21 @@ public function allEmbyUsers($newOnly = false) return false; }  
public function validateEmail($email) { return filter\_var(trim($email), FILTER\_VALIDATE\_EMAIL); }  
public function sanitizeEmail($email) { return filter\_var(trim($email), FILTER\_SANITIZE\_EMAIL); }  
public function sanitizeUserString($string) { return htmlspecialchars(trim($string)); }  
public function updateUser($id, $array) { if (!$id) { @@ -6211,6 +6234,7 @@ public function updateUser($id, $array) $this\->setAPIResponse('error', 'Username was set but empty', 409); return false; } $array\['username'\] = $this\->sanitizeUserString($array\['username'\]); if ($this\->usernameTaken($array\['username'\], $array\['username'\], $id)) { $this\->setAPIResponse('error', 'Username: ' . $array\['username'\] . ' is already taken', 409); return false; @@ -6221,6 +6245,12 @@ public function updateUser($id, $array) $this\->setAPIResponse('error', 'Email was set but empty', 409); return false; } if ($this\->validateEmail($array\['email'\])) { $array\['email'\] = $this\->sanitizeEmail($array\['email'\]); } else { $this\->setResponse(409, 'Email is not a valid email', \['email' => $array\['email'\]\]); return false; } if ($this\->usernameTaken($array\['email'\], $array\['email'\], $id)) { $this\->setAPIResponse('error', 'Email: ' . $array\['email'\] . ' is already taken', 409); return false; @@ -6260,6 +6290,9 @@ public function updateUser($id, $array) } $array\['password'\] = password\_hash($array\['password'\], PASSWORD\_BCRYPT); } if (array\_key\_exists('image', $array)) { $array\['image'\] = $this\->sanitizeUserString($array\['image'\]); } if (array\_key\_exists('register\_date', $array)) { $this\->setAPIResponse('error', 'Cannot update register date', 409); return false; @@ -6317,10 +6350,30 @@ public function addUser($array) $this\->setAPIResponse('error', 'Username was not supplied', 409); return false; } if ($username == '') { $this\->setResponse(409, 'Username was set but empty'); return false; } else { $username = $this\->sanitizeUserString($username); } if (!$password) { $this\->setAPIResponse('error', 'Password was not supplied', 409); return false; } if (!$email) { $this\->setAPIResponse('error', 'Email was set not supplied', 409); return false; } if ($email == '') { $this\->setAPIResponse('error', 'Email was set but empty', 409); return false; } if ($this\->validateEmail($email)) { $email = $this\->sanitizeEmail($email); } else { $this\->setResponse(409, 'Email is not a valid email', \['email' => $email\]); return false; } $this\->setLoggerChannel('User Management'); if ($this\->createUser($username, $password, $email)) { $this\->logger\->info('Account created for \[' . $username . '\]'); @@ -6340,10 +6393,21 @@ public function createUser($username, $password, $email = null) $this\->setAPIResponse('error', 'Username was set but empty', 409); return false; } $username = $this\->sanitizeUserString($username); if (!$password) { $this\->setAPIResponse('error', 'Password was set but empty', 409); return false; } if ($email == '') { $this\->setAPIResponse('error', 'Email was set but empty', 409); return false; } if ($this\->validateEmail($email)) { $email = $this\->sanitizeEmail($email); } else { $this\->setResponse(409, 'Email is not a valid email', \['email' => $email\]); return false; } if ($this\->usernameTaken($username, $email)) { $this\->setAPIResponse('error', 'Username: ' . $username . ' or Email: ' . $email . ' is already taken', 409); return false; @@ -6397,6 +6461,7 @@ public function updateGroup($id, $array) $this\->setAPIResponse('error', 'Group was set but empty', 409); return false; } $array\['group'\] = $this\->sanitizeUserString($array\['group'\]); if ($this\->isGroupNameTaken($array\['group'\], $id)) { $this\->setAPIResponse('error', 'Group name: ' . $array\['group'\] . ' is already taken', 409); return false; @@ -6476,6 +6541,7 @@ public function addGroup($array) $array\['default'\] = ($array\['default'\]) ?? 0; $array\['group\_id'\] = $this\->getNextGroupOrder() + 1; if (array\_key\_exists('group', $array)) { $array\['group'\] = $this\->sanitizeUserString($array\['group'\]); if ($this\->isGroupNameTaken($array\['group'\])) { $this\->setAPIResponse('error', 'Group name: ' . $array\['group'\] . ' is already taken', 409); return false;

CVE-2022-1347: added sanitizeUserString and sanitizeEmail functions · causefx/Organizr@a09d834

Multiple Stored XSS in GitHub repository causefx/organizr prior to 2.1.1810. This allows attackers to execute malicious scripts in the user's browser and it can lead to session hijacking, sensitive data exposure, and worse.

**Description**

The organizr application allows malicious javascript payload in multiple-input fields like "Categories", "Bookmark Tabs" and "Bookmark Categories" for which attacker can takeover the admin account.

**Proof of Concept**

1.Login to the co-admin account and go to go to "Settings" -> "Tab Editor".

2.Now in "Categories", "Bookmark Tabs" and "Bookmark Categories" Add options insert the below payloads:

          <img src=x onerror=alert(document.cookie)>
    
          <img src=x onerror=alert(document.domain)>
    
          <img src=x onerror=alert(document.location)>
    

3.Then login with the admin account and go to "Settings" -> "Tab Editor" and visit the "Categories", "Bookmark Tabs" and "Bookmark Categories" and you will see XSS will trigger in all those fields.

**PoC Video**

    https://drive.google.com/file/d/1n9FvXxzzmvtZc4VsdzOHl0oPxSnSDpMy/view?usp=sharing
    

**Impact**

This allows attackers to execute malicious scripts in the user's browser and it can lead to session hijacking, sensitive data exposure, and worse.

CVE-2022-1346: Multiple Stored XSS in organizr

Stored XSS due to no sanitization in the filename in GitHub repository causefx/organizr prior to 2.1.1810. This allows attackers to execute malicious scripts in the user's browser and it can lead to session hijacking, sensitive data exposure, and worse.

**Description**

The organizr application doesn't sanitize malicious javascript payload which leads to stored XSS and can also perform to the takeover admin account.

**Proof of Concept**

1.Login with Co-admin account and go to "Settings" -> "Image Manager" and upload any small size jpeg image and intercept the request on burp suite.

2.Then change the name of the uploaded image with the below XSS payload and forward the request:

         <img src=1 onerror=alert(1337)>.jpeg
    

3.Then login with admin account and go to "Settings" -> "Image Manager" and open the uploaded image by Co-admin you will see that XSS will trigger.

**PoC Video**

    https://drive.google.com/file/d/1X8-YyNkt8-MBLY2Btezn2Wel6HLjyhtu/view?usp=sharing
    

**Impact**

This allows attackers to execute malicious scripts in the user's browser and it can lead to session hijacking, sensitive data exposure, and worse.

CVE-2022-1344: Stored XSS due to no sanitization in the filename in organizr

Cross-site Scripting (XSS) vulnerability in Citrix StoreFront affects version 1912 before CU5 and version 3.12 before CU9

CTX377814

{{tooltipText}}

Security Bulletin | Medium | {{likeCount}} found this helpful | Created: {{articleFormattedCreatedDate}} | Modified: {{articleFormattedModifiedDate}}

**Description of Problem**

A reflected cross-site scripting (XSS) issue has been discovered in Citrix StoreFront when it is configured to use SAML authentication. If exploited, this issue would allow an attacker to execute client-side JavaScript in the same context as a legitimate user. This issue has the following identifier: 

CVE-ID 

Description 

Type 

Pre-requisites 

CVE-2022-27503 

Reflected Cross Site Scripting (XSS) 

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') 

A victim user must have a current session on a StoreFront that has been configured to use SAML authentication 

The issue affects the following supported versions of Citrix StoreFront: 

*   Citrix StoreFront 1912 LTSR up to and including CU4 (1912.0.4000) 
*   Citrix StoreFront 3.12 for 7.15 LTSR up to and including CU8 (3.12.8000) 

Affected versions of Citrix Storefront are included within the following supported versions of Citrix Virtual Apps and Desktops: 

*   Current Release (CR) versions of Citrix Virtual Apps and Desktops up to and including 2112 
*   Citrix Virtual Apps and Desktops 1912 LTSR up to and including CU4 
*   Citrix XenApp & XenDesktop 7.15 LTSR up to and including CU8 

**Mitigating Factors**

This issue only exists when Citrix StoreFront is configured to use SAML authentication. StoreFront deployments that have not been configured to use SAML authentication are unaffected. 

**What Customers Should Do**

Citrix recommends that affected customers upgrade to a fixed version as their patching schedule allows.  

 The issue has been addressed in the following supported Citrix StoreFront versions: 

*   Citrix StoreFront 2203 LTSR (2203.0.0) and later versions 
*   Citrix StoreFront 1912 LTSR CU5 (1912.0.5000) and later cumulative updates for 1912 LTSR 

The latest versions of Citrix StoreFront can be downloaded from the following location:   
https://www.citrix.com/downloads/storefront/

 These versions of Citrix StoreFront are included within the following supported versions of Citrix Virtual Apps and Desktops: 

*   Citrix Virtual Apps and Desktops 2203 LTSR and later versions 
*   Citrix Virtual Apps and Desktops 1912 LTSR CU5 and later cumulative updates for 1912 LTSR 

The latest versions of Citrix Virtual Apps and Desktops can be downloaded from the following location:   
https://www.citrix.com/downloads/citrix-virtual-apps-and-desktops/ 

   
A hotfix has been released to address this issue for Citrix StoreFront 3.12 for 7.15 LTSR. 

The hotfix for Citrix StoreFront 3.12 for 7.15 LTSR is available at the following location:    
https://support.citrix.com/article/CTX446966 

**Acknowledgements**

Citrix would like to thank Michał Brzezicki and Paweł Żurek for working with us to protect Citrix customers.

**What Citrix is Doing**

Citrix is notifying customers and channel partners about this potential security issue through the publication of this security bulletin on the Citrix Knowledge Center at https://support.citrix.com/securitybulletins.

**Obtaining Support on This Issue**

If you require technical assistance with this issue, please contact Citrix Technical Support. Contact details for Citrix Technical Support are available at https://www.citrix.com/support/open-a-support-case.

**Subscribe to Receive Alerts**

Citrix strongly recommends that all customers subscribe to receive alerts when a Citrix security bulletin is created or modified at https://support.citrix.com/user/alerts.

**Reporting Security Vulnerabilities to Citrix**

Citrix welcomes input regarding the security of its products and considers any and all potential vulnerabilities seriously. For details on our vulnerability response process and guidance on how to report security-related issues to Citrix, please see the following webpage: https://www.citrix.com/about/trust-center/vulnerability-process.html.

**Disclaimer**

This document is provided on an "as is" basis and does not imply any kind of guarantee or warranty, including the warranties of merchantability or fitness for a particular use. Your use of the information on the document is at your own risk. Citrix reserves the right to change or update this document at any time. Customers are therefore recommended to always view the latest version of this document directly from the Citrix Knowledge Center.

**Changelog**

Date

Change

2022-04-12

Initial Publication

CVE-2022-27503: Citrix StoreFront Security Bulletin for CVE-2022-27503

CTX370550

{{tooltipText}}

Security Bulletin | High | {{likeCount}} found this helpful | Created: {{articleFormattedCreatedDate}} | Modified: {{articleFormattedModifiedDate}}

**Description of Problem**

Vulnerabilities have been discovered in multiple Citrix SD-WAN products. These vulnerabilities, if exploited, could result in the following security issues: 

CVE-ID  

Description  

CWE  

Affected Products  

Pre-conditions 

CVE-2022-27505 

Reflected cross site scripting (XSS) 

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') 

Citrix SD-WAN Standard/Premium Edition Appliance 

Victim user must have a current session on the vulnerable device. 

CVE-2022-27506 

Hard-coded credentials allow administrators to access the shell via the SD-WAN CLI 

CWE-798: Use of Hard-coded Credentials 

Citrix SD-WAN Center Management Console, Citrix SD-WAN Standard/Premium Edition Appliance, and Citrix SD-WAN Orchestrator for On-Premises  

Admin access to SD-WAN CLI 

The following supported versions of Citrix SD-WAN are affected by the vulnerabilities 

*   CVE-2022-27505 – High Severity 
    

Citrix SD-WAN Standard/Premium Edition Appliance before 11.4.3a 

*   CVE-2022-27506 – Low Severity 
    

Citrix SD-WAN Center Management Console versions before 11.4.3 

Citrix SD-WAN Standard/Premium Edition Appliance versions before 11.4.1 

Citrix SD-WAN Orchestrator for On-Premises versions before 13.2.1 

**Mitigating Factors**

*   CVE-2022-27506: This issue is only exposed to administrators with access to the SD-WAN CLI 
    

**What Customers Should Do**

*   CVE-2022-27505:    
    Citrix recommends that affected customers upgrade to a fixed version as soon as possible. This issue has been addressed in the following supported Citrix SD-WAN versions: 
    

Citrix SD-WAN Standard/Premium Edition Appliance versions 11.4.3a and above 

*   CVE-2022-27506:  
    

Citrix recommends that affected customers upgrade to a fixed version as their patching schedule allows. This issue has been addressed in the following supported Citrix SD-WAN versions: 

Citrix SD-WAN Center Management Console versions 11.4.3 and above 

Citrix SD-WAN Standard/Premium Edition Appliance versions 11.4.1 and above 

Citrix SD-WAN Orchestrator for On-Premises versions 13.2.1 and above 

**Acknowledgements**

Citrix thanks Mattias Dewulf of Spinae for working with us to protect Citrix customers

**What Citrix is Doing**

Citrix is notifying customers and channel partners about this potential security issue through the publication of this security bulletin on the Citrix Knowledge Center at https://support.citrix.com/securitybulletins.

**Obtaining Support on This Issue**

If you require technical assistance with this issue, please contact Citrix Technical Support. Contact details for Citrix Technical Support are available at https://www.citrix.com/support/open-a-support-case.

**Subscribe to Receive Alerts**

Citrix strongly recommends that all customers subscribe to receive alerts when a Citrix security bulletin is created or modified at https://support.citrix.com/user/alerts.

**Reporting Security Vulnerabilities to Citrix**

Citrix welcomes input regarding the security of its products and considers any and all potential vulnerabilities seriously. For details on our vulnerability response process and guidance on how to report security-related issues to Citrix, please see the following webpage: https://www.citrix.com/about/trust-center/vulnerability-process.html.

**Disclaimer**

This document is provided on an "as is" basis and does not imply any kind of guarantee or warranty, including the warranties of merchantability or fitness for a particular use. Your use of the information on the document is at your own risk. Citrix reserves the right to change or update this document at any time. Customers are therefore recommended to always view the latest version of this document directly from the Citrix Knowledge Center.

**Changelog**

Date

Change

2022-04-12

Initial Publication

CVE-2022-27505: Citrix SD-WAN Security Bulletin for CVE-2022-27505 and CVE-2022-27506

A stored Cross-Site Scripting (XSS) vulnerability in the Missing Data Codes functionality of REDCap before 11.4.0 allows remote attackers to execute JavaScript code in the client's browser by storing said code as a Missing Data Code value. This can then be leveraged to execute a Cross-Site Request Forgery attack to escalate privileges to administrator.

Tag

#xss