A flaw in the way URLs are escaped and encoded in the org.apache.sling.xss.impl.XSSAPIImpl#getValidHref and org.apache.sling.xss.impl.XSSFilterImpl#isValidHref allows special crafted URLs to pass as valid, although they carry XSS payloads. The affected versions are Apache Sling X...
Product
org.apache.sling/org.apache.sling.xss.compat vulnerabilities
3 published CVES affecting org.apache.sling/org.apache.sling.xss.compat, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 3
- Critical
- 1
- High
- 0
- Medium
- 2
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest org.apache.sling/org.apache.sling.xss.compat CVEs
Newest publication first
-
MediumCVSS 6.1 EPSS 2.9%
-
MediumCVSS 6.1 EPSS 2.6% PoC
In the XSS Protection API module before 1.0.12 in Apache Sling, the encoding done by the XSSAPI.encodeForJSString() method is not restrictive enough and for some input patterns allows script tags to pass through unencoded, leading to potential XSS vulnerabilities.
-
CriticalCVSS 9.8 EPSS 3.7% PoC
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 rea...
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.