CVE-2022-43670: Apache Sling App CMS Cross-site Scripting Vulnerability

Summary

02/11/2022
Yes i
Moderate
5.4

CVE-2022-43670: Apache Sling App CMS vulnerable to Cross-site Scripting. Affects org.apache.sling:org.apache.sling.cms versions < 1.1.2. Fixed in 1.1.2. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Apache Sling App CMS is a content management system that allows users to create and manage web applications. It is built on top of the Apache Sling framework and provides features for managing content, including taxonomy management. This vulnerability affects versions 1.1.0 and prior of Sling App CMS.

Vulnerability Detail

The vulnerability identified as CVE-2022-43670 is a Cross-site Scripting (XSS) vulnerability in the taxonomy management feature of Apache Sling App CMS. An authenticated remote attacker can exploit this vulnerability to perform a reflected XSS attack. By injecting malicious scripts into the application, the attacker can execute arbitrary code in the context of the victim's browser. This can lead to various security risks, such as stealing sensitive information or performing unauthorized actions on behalf of the victim.

How To Fix

Minimum fixed version

1.1.2

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is recommended to apply the official fix by upgrading to the latest version of Apache Sling App CMS.

Conclusion

The Cross-site Scripting vulnerability in Apache Sling App CMS version 1.1.0 and prior can allow an authenticated remote attacker to perform a reflected XSS attack. To mitigate this vulnerability, it is recommended to upgrade to version 1.1.2 or later. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.apache.sling:org.apache.sling.cms →

Share this vulnerability

FAQ

Apache Sling App CMS is a content management system that allows users to create and manage web applications.

Cross-site Scripting (XSS) is a type of security vulnerability that allows attackers to inject malicious scripts into web pages viewed by other users.

An attacker with authenticated access to the Apache Sling App CMS can inject malicious scripts into the taxonomy management feature, which will be executed by the victim's browser when viewing the affected page.

Exploiting this vulnerability can lead to various security risks, including stealing sensitive information, performing unauthorized actions on behalf of the victim, or spreading malware.

Yes, users of Apache Sling App CMS should upgrade to version 1.1.2 or later to fix this vulnerability.

Related vulnerabilities

Recent vulnerabilities recorded for org.apache.sling:org.apache.sling.cms.

How To Fix

Minimum fixed version

1.1.2

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback