CVE-2015-2944: Cross-Site Scripting Vulnerabilities in Apache Sling

Summary

13/05/2022
Yes i
Moderate
Not published

CVE-2015-2944: Improper Neutralization of Input During Web Page Generation in Apache Sling. Affects org.apache.sling:org.apache.sling.api versions < 2.2.2. Fixed in 2.2.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 Your last release was probably never penetration tested 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 is a web framework for building content-oriented applications. It provides a RESTful framework to access content and exposes content through Apache Sling's Resource API. The Apache Sling API and Apache Sling Servlets Post are two components of Apache Sling that are affected by this vulnerability.

Vulnerability Detail

The vulnerability, identified as CVE-2015-2944, is an instance of multiple cross-site scripting (XSS) vulnerabilities in Apache Sling API before version 2.2.2 and Apache Sling Servlets Post before version 2.1.2. These vulnerabilities allow remote attackers to inject arbitrary web script or HTML via the URI. The specific affected classes are org/apache/sling/api/servlets/HtmlResponse and org/apache/sling/servlets/post/HtmlResponse. The impact of these vulnerabilities can lead to unauthorized access, data theft, or the execution of malicious code on the affected system.

How To Fix

Latest published version: 3.0.2 as of 22 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.2.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 essential to apply the recommended fix by upgrading to the patched versions of Apache Sling API and Apache Sling Servlets Post.

Conclusion

In conclusion, the CVE-2015-2944 vulnerability in Apache Sling API and Apache Sling Servlets Post exposes applications to cross-site scripting attacks. To mitigate this vulnerability, it is crucial to upgrade to the patched versions of the affected components. For further support on vulnerability remediation, please contact DevNack.com.

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

Share this vulnerability

FAQ

Apache Sling is a web framework for building content-oriented applications. It provides a RESTful framework to access content and exposes content through Apache Sling's Resource API.

Cross-site scripting (XSS) is a type of security vulnerability that allows attackers to inject malicious scripts into web pages viewed by other users. This can lead to unauthorized access, data theft, or the execution of malicious code.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities in software using just the pom.xml file.

The impact of this vulnerability can lead to unauthorized access, data theft, or the execution of malicious code on the affected system.

There are no known workarounds for this vulnerability. It is crucial to apply the recommended fix by upgrading to the patched versions of Apache Sling API and Apache Sling Servlets Post.

Related vulnerabilities

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

How To Fix

Latest published version: 3.0.2 as of 22 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.2.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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.