An issue was discovered in Kirby 2.5.12. The application allows malicious HTTP requests to be sent in order to trick a user into adding web pages.

    # Exploit Title:​​ Kirby CMS 2.5.12 - Cross-Site Scripting
    # Date: 2018-07-22
    # Exploit Author: Zaran Shaikh
    # Version: ​2.5.12
    # CVE :  ​NA
    # Category: ​Web Application
    
    # Description
    # The application allows user injected payload which can lead to Stored
    # Cross Site Scripting.
    
    # Proof of Concept
    # 1. Visit the application as low priv user
    # 2. Go to add page option
    # 3. Under title, enter any XSS payload like:
    
    <script>alert("XSS");</script>
    
    # 4. Upon the payload being injected, the subsequent page is triggered
    # with XSS

CVE-2018-14520: Offensive Security’s Exploit Database Archive

An issue was discovered in Kirby 2.5.12. The delete page functionality suffers from a CSRF flaw. A remote attacker can craft a malicious CSRF page and force the user to delete a page.

**Cross Site Request Forgery - Kirby CMS**

Cross Site Request Forgery - Kirby CMS  
By- Zaran Shaikh

Hi Readers,

Welcome to my blog. I am a inquisitive learner in the world of Cyber Security and will love to share my research and other stuff in coming time.

Since a while I have been fascinated with the concept of 0 days and started learning more on the topic. While coming across open source applications, I decided to explore Kirby CMS. I found multiple vulnerabilities in it, of which I am mentioning about Cross Site Request Forgery.  
Title of the Vulnerability:  Stored XSS  
Vulnerability Class: Web Application Exploits.

**Technical Details & Description**: The application allows malicious HTTP requests to be sent in order to trick a user into adding/ deleting web pages.

CVE ID allocated: - Undisclosed.

**Product & Service Introduction**: Kirby CMS

**Steps to Re-Produce –**  
1.       Visit the application  
2.       Go to add page option  
3.       Create a crafted HTTP page with delete/ add option and host it on a server. Upon sending the link to a user and upon click, it gets triggered and the page is added/deleted  
4\. Payload:  
<html>  
  <body>  
  <script>history.pushState('', '', '/')</script>  
    <form action="http://localhost/kirby/panel/pages/csrf-test-page/delete">  
      <input type="hidden" name="&#95;redirect" value="site&#47;subpages" />  
      <input type="submit" value="Submit request" />  
    </form>  
    <script>  
      document.forms\[0\].submit();  
    </script>  
  </body>  
</html>

**Exploitation Technique:** A attacker can inject perform severe actions including account takeover.  
**Severity Level**: High  
**Security Risk:**  
The presence of such a risk can lead to data loss,privilege escalation etc.

**Affected Product Version**:  Kirby 2.5.12  
**Solution - Fix & Patch:** The application code should be configured to implement anti csrf tokens.

POCs:

  

**Stored XSS - Kirby CMS**

By- Zaran Shaikh

Hi Readers,

Welcome to my blog. I am a inquisitive learner in the world of Cyber Security and will love to share my research and other stuff in coming time.

Since a while I have been fascinated with the concept of 0 days and started learning more on the topic. While coming across open source applications, I decided to explore Kirby CMS. I found multiple vulnerabilities in it, of which I am mentioning about Stored Cross Site Scripting

**Title of the Vulnerability**:  Stored XSS

**Vulnerability Class**: Web Application Exploits.

**Technical Details & Description**: The application allows user injected payload which can lead to Stored Cross Site Scripting.

CVE ID allocated: - Undisclosed.

Product & Service Introduction: Kirby CMS

Steps to Re-Produce –

1.       Visit the application

2.       Go to add page option

3.       Under title, enter any XSS payload like: <script>alert("XSS");</script>

4.       Upon the payload being injected, the subsequent page is triggered with XSS.

**Exploitation Technique**: A attacker can inject malicious xss payloads to steal user data.

**Severity Level**: High

**Security Risk**:

The presence of such a risk can lead to data loss, xss shell uploads etc

**Affected Product Version**:  Kirby 2.5.12

**Solution - Fix & Patch**: The application code should be configured to implement strict input validation to prevent XSS payloads.

POCs:

CVE-2018-14519: Zaran's Security Research Blog

An issue was discovered in Artica Proxy 4.30.000000. There is a XSS vulnerability via the password parameter in /fw.login.php.

**CVE-2022-37153**

There is a XSS vulnerability in Artica Proxy 4.30.000000

vulname: Artica Proxy reflected XSS

vulnerable page: /fw.login.php

vulnerable param: password

payload: "><script>alert(1)</script>

FOFA: icon\_hash="-27821316"

CVE-2022-37153: GitHub - Fjowel/CVE-2022-37153: There is a XSS  vulnerability  in Artica Proxy 4.30.000000

Stored cross-site scripting vulnerability in Exment ((PHP8) exceedone/exment v5.0.2 and earlier and exceedone/laravel-admin v3.0.0 and earlier, (PHP7) exceedone/exment v4.4.2 and earlier and exceedone/laravel-admin v2.2.2 and earlier) allows a remote authenticated attacker to inject an arbitrary script.

CVE-2022-38089: Document

ServiceNow through San Diego Patch 4b and Patch 6 allows reflected XSS in the logout functionality.

 

 Loading...

Skip to page content

Skip to page content

CVE-2022-38463: - - Now Support Portal

ServiceNow through San Diego Patch 3 allows XSS via the name field during creation of a new dashboard for the Performance Analytics dashboard.

CVE-2022-38172: - - Now Support Portal

Jenkins Git Plugin 4.11.4 and earlier does not properly mask (i.e., replace with asterisks) credentials in the build log provided by the Git Username and Password (`gitUsernamePassword`) credentials binding.

This advisory announces vulnerabilities in the following Jenkins deliverables:

*   CollabNet Plugins Plugin
*   Git Plugin
*   Job Configuration History Plugin
*   Kubernetes Continuous Deploy Plugin

**Descriptions****Improper masking of credentials in Git Plugin**

**SECURITY-2796 / CVE-2022-38663**  
**Severity (CVSS):** Medium  
**Affected plugin: git**  
**Description:**

Git Plugin 4.11.4 and earlier does not properly mask (i.e., replace with asterisks) credentials in the build log provided by the Git Username and Password (gitUsernamePassword) credentials binding. Usernames are masked instead of passwords in cases when usernames are not set to be treated as secret.

Git Plugin 4.11.5 properly masks credentials in the build log provided by the Git Username and Password (gitUsernamePassword) credentials binding. As a side effect of the fix, usernames currently set to be not masked will lose their current (unintentional) masking.

**Stored XSS vulnerability in Job Configuration History Plugin**

**SECURITY-2765 / CVE-2022-38664**  
**Severity (CVSS):** High  
**Affected plugin: jobConfigHistory**  
**Description:**

Job Configuration History Plugin 1165.v8cc9fd1f4597 and earlier does not escape the job name on the System Configuration History page.

This results in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to configure job names.

Job Configuration History Plugin 1166.vc9f255f45b\_8a escapes the job name on the System Configuration History page.

**RabbitMQ password stored in plain text by CollabNet Plugins Plugin**

**SECURITY-2157 / CVE-2022-38665**  
**Severity (CVSS):** Low  
**Affected plugin: collabnet**  
**Description:**

CollabNet Plugins Plugin 2.0.8 and earlier stores a RabbitMQ password unencrypted in its global configuration file hudson.plugins.collabnet.share.TeamForgeShare.xml on the Jenkins controller as part of its configuration.

This password can be viewed by users with access to the Jenkins controller file system.

CollabNet Plugins Plugin 2.0.9 no longer includes the EventQ feature that accepts RabbitMQ credentials. The RabbitMQ password will be removed from the configuration file once it is saved again.

**RCE vulnerability in Kubernetes Continuous Deploy Plugin**

**SECURITY-2448 / CVE-2021-25738**  
**Severity (CVSS):** High  
**Affected plugin: kubernetes-cd**  
**Description:**

Kubernetes Continuous Deploy Plugin 2.3.1 and earlier bundles a version of Kubernetes Java Client library with the vulnerability CVE-2021-25738 that does not configure its YAML parser to prevent the instantiation of arbitrary types.

This results in a remote code execution (RCE) vulnerability exploitable by users able to provide YAML input files to Kubernetes Continuous Deploy Plugin’s build step.

As of publication of this advisory, there is no fix.

**Severity**

*   SECURITY-2157: Low
*   SECURITY-2448: High
*   SECURITY-2765: High
*   SECURITY-2796: Medium

**Affected Versions**

*   **CollabNet Plugins Plugin** up to and including 2.0.8
*   **Git Plugin** up to and including 4.11.4
*   **Job Configuration History Plugin** up to and including 1165.v8cc9fd1f4597
*   **Kubernetes Continuous Deploy Plugin** up to and including 2.3.1

**Fix**

*   **CollabNet Plugins Plugin** should be updated to version 2.0.9
*   **Git Plugin** should be updated to version 4.11.5
*   **Job Configuration History Plugin** should be updated to version 1166.vc9f255f45b\_8a

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:

*   Kubernetes Continuous Deploy Plugin

Learn why we announce these issues.

**Credit**

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

*   **Jordy Versmissen** for SECURITY-2448
*   **Kevin Guerroudj, CloudBees, Inc.** for SECURITY-2765
*   **Peter Darton, i2group.com, and independently, Stefano Mazzucco, Mindera** for SECURITY-2796
*   **Son Nguyen (@s0nnguy3n\_)** for SECURITY-2157

CVE-2022-38663: Jenkins Security Advisory 2022-08-23

Jenkins Job Configuration History Plugin 1165.v8cc9fd1f4597 and earlier does not escape the job name on the System Configuration History page, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to configure job names.

CVE-2022-38664: Jenkins Security Advisory 2022-08-23

Jenkins CollabNet Plugins Plugin 2.0.8 and earlier stores a RabbitMQ password unencrypted in its global configuration file on the Jenkins controller where it can be viewed by users with access to the Jenkins controller file system.

CVE-2022-38665: Jenkins Security Advisory 2022-08-23

Authenticated (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in amCharts: Charts and Maps plugin <= 1.4 at WordPress.

 Verified

 Fixed

**5.4**

CVSS 3.1 score Medium severity

Monitoring Coming soon

PSID 

138b6f2f09e2

Classification 

Cross Site Scripting (XSS)

OWASP Top 10 

A7: Cross-Site Scripting (XSS)

Required privilege 

Requires contributor or higher role user authentication.

Publicly disclosed

2022-08-09

**Details**

Authenticated Stored Cross-Site Scripting (XSS) vulnerability discovered by Ngo Van Thien (Patchstack Alliance) in WordPress amCharts: Charts and Maps plugin (versions <= 1.4).

**Solution**

Update the WordPress amCharts: Charts and Maps plugin to the latest available version (at least 1.4.1).

**References**

Tag

#xss