CVE-2013-4390 — org.apache.sling.auth.core
MEDIUMFix: apache/sling-org-apache-sling-auth-core@d1cd9aaCVE-2013-4390 is a medium-severity (CVSS 4.7) Improper Input Validation vulnerability in org.apache.sling:org.apache.sling.auth.core. A fix is available for org.apache.sling:org.apache.sling.auth.core — see the affected versions and patch details below.
Apache Sling Auth Core bundle vulnerable to Open Redirection
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.apache.sling:org.apache.sling.auth.coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Open redirect vulnerability in the AbstractAuthenticationFormServlet in the Auth Core (org.apache.sling.auth.core) bundle before 1.1.4 in Apache Sling allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a URL in the resource parameter, related to "a custom login form and XSS."
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.sling:org.apache.sling.auth.core | all versions | 1.1.4org.apache.sling:org.apache.sling.auth.core:1.1.4 |
Affected Products
slingapachesling auth core componentapacheDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.sling:org.apache.sling.auth.core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.sling:org.apache.sling.auth.core to 1.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-4390 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2013-4390 in your dependencies?
Find it across Maven, including transitive dependencies.