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

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.

CVE-2021-42136

An XSS issue was discovered in MantisBT before 2.25.3. Improper escaping of a Plugin name allows execution of arbitrary code (if CSP allows it) in manage_plugin_page.php and manage_plugin_uninstall.php when a crafted plugin is installed.

![dregad](https://secure.gravatar.com/avatar/d76f8d74339c20fb921287d3c607d102?d=identicon&r=G&s=80)

dregad

2022-02-26 01:58

developer   ~0066307

CVE-2022-26144 assigned

![atrol](https://secure.gravatar.com/avatar/73c62116c4c5b1c7c379affab8284f1d?d=identicon&r=G&s=80)

atrol

2022-02-26 05:25

developer   ~0066308

We are executing arbitrary plugin code that can't be controlled by us, as there is no sandbox concept for plugins.  
This means that you have to trust the **whole** plugin code.

@dregad not sure I am missing something.  
Do you confirm that preventing the output of a crafted plugin name is just a minor security measure and not a hurdle for the real bad guys?

![dregad](https://secure.gravatar.com/avatar/d76f8d74339c20fb921287d3c607d102?d=identicon&r=G&s=80)

dregad

2022-03-01 02:26

developer   ~0066316

> This means that you have to trust the whole plugin code.

Yes of course, there is always such a risk when executing foreign code in your environment.

Actually this XSS is a regression that I introduced with MantisBT master 11a6d0de (see 0026142) so I thought it should at least be corrected (the vulnerability it was originally fixed in 0012231).

> preventing the output of a crafted plugin name is just a minor security measure

That's exactly what this is.

> not a hurdle for the real bad guys

Not really sure what you mean by that though...

![atrol](https://secure.gravatar.com/avatar/73c62116c4c5b1c7c379affab8284f1d?d=identicon&r=G&s=80)

atrol

2022-03-01 16:40

developer   ~0066317

> Not really sure what you mean by that though...

Attackers (bad guys) don't rely on the non-sanitized plugin name to inject code.  
It's an easy job for them to find / use one of many other available options to execute malicious code in a plugin.

CVE-2022-26144: 0029688: CVE-2022-26144: XSS in manage_plugin_page.php and manage_plugin_uninstall.php

CMSimple 5.4 is vulnerable to Cross Site Scripting (XSS) via the file upload feature.

CVE-2021-43742

Cross site scripting (XSS) vulnerability in tramyardg hotel-mgmt-system, allows attackers to execute arbitrary code when when /admin.php is loaded.

Permalink

Browse files

\+ sanitize xss function

* Loading branch information

![@tramyardg](https://avatars.githubusercontent.com/u/5623994?s=40&v=4)

tramyardg committed

Mar 28, 2022

1 parent 2a9161e commit 3aa5fdd736927f4ba8d4b7efbba850a258ab42ce

Showing with **7 additions** and **0 deletions**.

1. +7 −0 app/Util.php

7 app/Util.php

Show comments View file

@@ -36,4 +36,11 @@ public static function displayAlertV2($message, $type)

' . $message\["footer"\] . '

</div>';

}

 

public static function sanitize\_xss($value)

{

return htmlspecialchars(strip\_tags($value));

}

 

 

}

**0 comments on commit `3aa5fdd`**

Please sign in to comment.

CVE-2022-27475: + sanitize xss function · tramyardg/hotel-mgmt-system@3aa5fdd

stored xss due to unsantized anchor url in GitHub repository alvarotrigo/fullpage.js prior to 4.0.4. stored xss .

@@ -57,12 +57,12 @@ export function addSlidesNavigation(section){

 

for(var i\=0; i< numSlides; i++){

var slide \= utils.$(SLIDE\_SEL, sectionElem)\[i\];

utils.appendTo(utils.createElementFromHTML('<li><a href="#">'+ getBulletLinkName(i, 'Slide', slide) +'</a></li>'), utils.$('ul', nav)\[0\] );

utils.appendTo(utils.createElementFromHTML('<li><a href="#">'+ encodeURI(getBulletLinkName(i, 'Slide', slide)) +'</a></li>'), utils.$('ul', nav)\[0\] );

}

 

//centering it

utils.css(nav, {'margin-left': '-' + (nav.innerWidth/2) + 'px'});

 

var activeSlideIndex \= section.activeSlide ? section.activeSlide.index() : 0;

utils.addClass(utils.$('a', utils.$('li', nav)\[activeSlideIndex\] ), ACTIVE);

}

}

CVE-2022-1330: Merge pull request #4360 from ranjit-git/ranjit-git-patch-1 · alvarotrigo/fullPage.js@e7a5db4

Jenkins Subversion Plugin 2.15.3 and earlier does not escape the name and description of List Subversion tags (and more) parameters on views displaying parameters, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/Configure permission.

This advisory announces vulnerabilities in the following Jenkins deliverables:

*   Credentials Plugin
*   CVS Plugin
*   Extended Choice Parameter Plugin
*   Gerrit Trigger Plugin
*   Git Parameter Plugin
*   Google Compute Engine Plugin
*   Jira Plugin
*   Job Generator Plugin
*   Mask Passwords Plugin
*   Node and Label parameter Plugin
*   Pipeline: Deprecated Groovy Libraries Plugin
*   promoted builds Plugin
*   Publish Over FTP Plugin
*   Subversion Plugin

**Descriptions****Stored XSS vulnerabilities in multiple plugins providing additional parameter types**

**SECURITY-2617 / CVE-2022-29036 (Credentials), CVE-2022-29037 (CVS), CVE-2022-29038 (Extended Choice Parameter), CVE-2022-29039 (Gerrit Trigger), CVE-2022-29040 (Git Parameter), CVE-2022-29041 (Jira), CVE-2022-29042 (Job Generator), CVE-2022-29043 (Mask Passwords), CVE-2022-29044 (Node and Label Parameter), CVE-2022-29045 (promoted builds), CVE-2022-29046 (Subversion)**

Multiple plugins do not escape the name and description of the parameter types they provide:

*   Credentials Plugin 1111.v35a\_307992395 and earlier (SECURITY-2690 / CVE-2022-29036)
    
*   CVS Plugin 2.19 and earlier (SECURITY-2700 / CVE-2022-29037)
    
*   Extended Choice Parameter Plugin 346.vd87693c5a\_86c and earlier (SECURITY-2704 / CVE-2022-29038)
    
*   Gerrit Trigger Plugin 2.35.2 and earlier (SECURITY-2703 / CVE-2022-29039)
    
*   Git Parameter Plugin 0.9.15 and earlier (SECURITY-2699 / CVE-2022-29040)
    
*   Jira Plugin 3.7 and earlier (SECURITY-2691 / CVE-2022-29041)
    
*   Job Generator 1.22 and earlier (SECURITY-2263 / CVE-2022-29042)
    
*   Mask Passwords Plugin 3.0 and earlier (SECURITY-2701 / CVE-2022-29043)
    
*   Node and Label parameter Plugin 1.10.3 and earlier (SECURITY-2702 / CVE-2022-29044)
    
*   promoted builds Plugin 873.v6149db\_d64130 and earlier (SECURITY-2692 / CVE-2022-29045)
    
*   Subversion Plugin 2.15.3 and earlier (SECURITY-2698 / CVE-2022-29046)
    

This results in stored cross-site scripting (XSS) vulnerabilities exploitable by attackers with Item/Configure permission.

Exploitation of these vulnerabilities requires that parameters are listed on another page, like the "Build With Parameters" and "Parameters" pages provided by Jenkins (core), and that those pages are not hardened to prevent exploitation. Jenkins (core) has prevented exploitation of vulnerabilities of this kind on the "Build With Parameters" and "Parameters" pages since 2.44 and LTS 2.32.2 as part of the SECURITY-353 / CVE-2017-2601 fix. Additionally, the following plugins have been updated to list parameters in a way that prevents exploitation by default.

*   Maven Release Plugin 0.16.3 (SECURITY-2669)
    
*   Pipeline: Build Step Plugin 2.17 and 2.15.2 (SECURITY-2611)
    
*   Pipeline: Input Step Plugin 447.v95e5a\_6e3502a\_ and 2.12.1 (SECURITY-2674)
    
*   promoted builds Plugin 876.v99d29788b\_36b\_ and 3.10.1 (SECURITY-2670)
    
*   Rebuilder Plugin 1.33.1 (SECURITY-2671)
    
*   Release Plugin 2.14 (SECURITY-2672)
    

Older releases of these plugins allow exploitation of the vulnerabilities listed above.

As of publication of this advisory, the following plugins have not yet been updated to list parameters in a way that prevents exploitation of these vulnerabilities:

*   Coordinator Plugin (SECURITY-2668)
    
*   Show Build Parameters Plugin (SECURITY-2325)
    
*   Unleash Maven Plugin (SECURITY-2673)
    

These are not vulnerabilities in these plugins. Only plugins defining parameter types can be considered to be vulnerable to this issue.

Some plugins both define parameter types and implement a page listing parameters, so they can appear in multiple lists and may have both a security fix and a security hardening applied.

The following plugins have been updated to escape the name and description of the parameter types they provide in the versions specified:

*   Credentials Plugin 1112.vc87b\_7a\_3597f6, 1087.1089.v2f1b\_9a\_b\_040e4, 1074.1076.v39c30cecb\_0e2, and 2.6.1.1
    
*   CVS Plugin 2.19.1
    
*   Gerrit Trigger Plugin 2.35.3
    
*   Git Parameter Plugin 0.9.16
    
*   Jira Plugin 3.7.1 and 3.6.1
    
*   Mask Passwords Plugin 3.1
    
*   Node and Label parameter Plugin 1.10.3.1
    
*   promoted builds Plugin 876.v99d29788b\_36b\_ and 3.10.1
    
*   Subversion Plugin 2.15.4
    

As of publication of this advisory, there is no fix available for the following plugins:

*   Extended Choice Parameter Plugin (SECURITY-2704 / CVE-2022-29038)
    
*   Job Generator (SECURITY-2263 / CVE-2022-29042)
    

**Untrusted users can modify some Pipeline libraries in Pipeline: Deprecated Groovy Libraries Plugin**

**SECURITY-1951 / CVE-2022-29047**

Multibranch Pipelines by default limit who can change the Pipeline definition from the Jenkinsfile. This is useful for SCMs like GitHub: Jenkins can build content from users without commit access, but who can submit pull requests, without granting them the ability to modify the Pipeline definition. In that case, Jenkins will just use the Pipeline definition in the pull request’s destination branch instead.

In Pipeline: Deprecated Groovy Libraries Plugin 564.ve62a\_4eb\_b\_e039 and earlier the same protection does not apply to uses of the library step with a retriever argument pointing to a library in the current build’s repository and branch (e.g., library(…, retriever: legacySCM(scm))). This allows attackers able to submit pull requests (or equivalent), but not able to commit directly to the configured SCM, to effectively change the Pipeline behavior by changing the library behavior in their pull request, even if the Pipeline is configured to not trust them.

Pipeline: Deprecated Groovy Libraries Plugin 566.vd0a\_a\_3334a\_555 and 2.21.3 aborts library retrieval if the library would be retrieved from the same repository and revision as the current build, and the revision being built is untrusted.

**CSRF vulnerability in Subversion Plugin**

**SECURITY-2075 / CVE-2022-29048**

Subversion Plugin 2.15.3 and earlier does not require POST requests for several form validation methods, resulting in cross-site request forgery (CSRF) vulnerabilities.

These vulnerabilities allow attackers to connect to an attacker-specified URL.

Subversion Plugin 2.15.4 requires POST requests for the affected form validation methods.

**Promotion names in promoted builds Plugin are not validated when using Job DSL**

**SECURITY-2655 / CVE-2022-29049**

promoted builds Plugin provides dedicated support for defining promotions using Job DSL Plugin.

promoted builds Plugin 873.v6149db\_d64130 and earlier does not validate the names of promotions defined in Job DSL. This allows attackers with Job/Configure permission to create a promotion with an unsafe name. As a result, the promotion name could be used for cross-site scripting (XSS) or to replace other config.xml files.

promoted builds Plugin 876.v99d29788b\_36b\_ and 3.10.1 validates the name of promotions.

**CSRF vulnerability and missing permission checks in Publish Over FTP Plugin**

**SECURITY-2321 / CVE-2022-29050 (CSRF), CVE-2022-29051 (missing permission check)**

Publish Over FTP Plugin 1.16 and earlier does not perform permission checks in methods implementing form validation.

This allows attackers with Overall/Read permission to connect to an FTP server using attacker-specified credentials.

Additionally, these form validation methods do not require POST requests, resulting in a cross-site request forgery (CSRF) vulnerability.

Publish Over FTP Plugin 1.17 requires POST requests and appropriate permissions for the affected form validation methods.

**Private key stored in plain text by Google Compute Engine Plugin**

**SECURITY-2045 / CVE-2022-29052**

Google Compute Engine Plugin 4.3.8 and earlier stores private keys unencrypted in cloud agent config.xml files on the Jenkins controller as part of its configuration.

These private keys can be viewed by users with Agent/Extended Read permission or access to the Jenkins controller file system.

Google Compute Engine Plugin 4.3.9 stores private keys encrypted.

**Severity**

*   SECURITY-1951: High
*   SECURITY-2045: Medium
*   SECURITY-2075: Medium
*   SECURITY-2321: Medium
*   SECURITY-2617: High
*   SECURITY-2655: High

**Affected Versions**

*   **Credentials Plugin** up to and including 1111.v35a\_307992395
*   **CVS Plugin** up to and including 2.19
*   **Extended Choice Parameter Plugin** up to and including 346.vd87693c5a\_86c
*   **Gerrit Trigger Plugin** up to and including 2.35.2
*   **Git Parameter Plugin** up to and including 0.9.15
*   **Google Compute Engine Plugin** up to and including 4.3.8
*   **Jira Plugin** up to and including 3.7
*   **Job Generator Plugin** up to and including 1.22
*   **Mask Passwords Plugin** up to and including 3.0
*   **Node and Label parameter Plugin** up to and including 1.10.3
*   **Pipeline: Deprecated Groovy Libraries Plugin** up to and including 564.ve62a\_4eb\_b\_e039
*   **promoted builds Plugin** up to and including 873.v6149db\_d64130
*   **Publish Over FTP Plugin** up to and including 1.16
*   **Subversion Plugin** up to and including 2.15.3

**Fix**

*   **Credentials Plugin** should be updated to version 1112.vc87b\_7a\_3597f6, 1087.1089.v2f1b\_9a\_b\_040e4, 1074.1076.v39c30cecb\_0e2, or 2.6.1.1
*   **CVS Plugin** should be updated to version 2.19.1
*   **Gerrit Trigger Plugin** should be updated to version 2.35.3
*   **Git Parameter Plugin** should be updated to version 0.9.16
*   **Google Compute Engine Plugin** should be updated to version 4.3.9
*   **Jira Plugin** should be updated to version 3.7.1 or 3.6.1
*   **Mask Passwords Plugin** should be updated to version 3.1
*   **Node and Label parameter Plugin** should be updated to version 1.10.3.1
*   **Pipeline: Deprecated Groovy Libraries Plugin** should be updated to version 566.vd0a\_a\_3334a\_555 or 2.21.3
*   **promoted builds Plugin** should be updated to version 876.v99d29788b\_36b\_ or 3.10.1
*   **Publish Over FTP Plugin** should be updated to version 1.17
*   **Subversion Plugin** should be updated to version 2.15.4

These versions include fixes to the vulnerabilities described above. All prior versions are considered to be affected by these vulnerabilities unless otherwise indicated.

As of publication of this advisory, no fixes are available for the following plugins:

*   Extended Choice Parameter Plugin
*   Job Generator Plugin

**Credit**

The Jenkins project would like to thank the reporters for discovering and reporting these vulnerabilities:

*   **Daniel Beck, CloudBees, Inc.** for SECURITY-2045
*   **James Nord, CloudBees, Inc. and Daniel Beck, CloudBees, Inc.** for SECURITY-2075
*   **James Nord, CloudBees, Inc. and Jesse Glick, CloudBees, Inc.** for SECURITY-1951
*   **Kevin Guerroudj, CloudBees, Inc. and Wadeck Follonier, CloudBees, Inc.** for SECURITY-2655
*   **Kevin Guerroudj, CloudBees, Inc., Wadeck Follonier, CloudBees, Inc., and Daniel Beck, CloudBees, Inc.** for SECURITY-2617
*   **Kevin Guerroudj, Justin Philip, Marc Heyries** for SECURITY-2321

CVE-2022-29046: Jenkins Security Advisory 2022-04-12

A cross-site request forgery (CSRF) vulnerability in Jenkins Subversion Plugin 2.15.3 and earlier allows attackers to connect to an attacker-specified URL.

Tag

#xss