CVE-2016-6798

Name: CVE-2016-6798
Creator: NVD / NIST
Published: 2017-07-19T15:29:00.213+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 3.67%

Last modified Jun 17, 2026

CVE-2016-6798 is a vulnerability of currently unknown severity. In the XSS Protection API module before 1.0.12 in Apache Sling, the method XSS.getValidXML() uses an insecure SAX parser to validate the input string, which allows for XXE attacks in all scripts which use this method to validate user input, potentially allowing an attacker to read sensitive data on the filesystem, perform same-site-request-forgery (SSRF), port-scanning behind the firewall or DoS the application.. EPSS estimates a 3.67% chance of exploitation in the next 30 days.

Description

In the XSS Protection API module before 1.0.12 in Apache Sling, the method XSS.getValidXML() uses an insecure SAX parser to validate the input string, which allows for XXE attacks in all scripts which use this method to validate user input, potentially allowing an attacker to read sensitive data on the filesystem, perform same-site-request-forgery (SSRF), port-scanning behind the firewall or DoS the application.

Metrics

EPSS Probability

3.67%

88.2th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-611

Affected Software

Vendor	Product	Versions
Apache	Sling	<= 1.0.10

References

http://www.securityfocus.com/bid/99873Third Party Advisory, VDB Entry
https://lists.apache.org/thread.html/b72c3a511592ec70729b3ec2d29302b6ce87bbeab62d4745617a6bd0%40%3Cdev.sling.apache.org%3E
http://www.securityfocus.com/bid/99873Third Party Advisory, VDB Entry
https://lists.apache.org/thread.html/b72c3a511592ec70729b3ec2d29302b6ce87bbeab62d4745617a6bd0%40%3Cdev.sling.apache.org%3E

Timeline

Published: Jul 19, 2017
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2016-6798?

How severe is CVE-2016-6798?

Severity scoring for CVE-2016-6798 is pending analysis. The EPSS model estimates a 3.67% probability of exploitation in the next 30 days.

How do I fix CVE-2016-6798?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2016-6798?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST