SolrApplication · Apache
CVE-2015-8796
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-site scripting (XSS) vulnerability in webapp/web/js/scripts/schema-browser.js in the Admin UI in Apache Solr before 5.3 allows remote attackers to inject arbitrary web script or HTML via a crafted schema-browse URL.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCross-site scripting (XSS) vulnerability in Apache Solr Admin UI's schema-browser.js file. The vulnerability allows remote attackers to inject arbitrary web script or HTML via crafted schema-browse URLs, exploiting insufficient input sanitization in the affected JavaScript component.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
SolrApplication
<= 5.2.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Apache Solr versionAccess the Solr Admin UI (typically at /solr/admin/) and check the version displayed in the header or about page. Alternatively, check for a VERSION or CHANGES.txt file in the Solr installation directory.Affected if The installed version is 5.2.1 or any earlier version (5.0.0 through 5.2.1)
-
Confirm Admin UI is accessibleNavigate to the Solr Admin interface path (such as /solr/) in a web browser or via curl to verify the administrative interface is reachable.Affected if The Admin UI is exposed without authentication or access controls
-
Locate the schema-browser.js fileWithin the Solr installation, locate the schema-browser.js file under the Admin UI's static assets (typically in the /solr-webapp/webapp/ or similar static content directory).Affected if The schema-browser.js file exists and is served by the Admin UI
-
Test schema-browser URL parameterAccess a URL containing the schema-browser parameter (such as /solr/#/collection_name/schema-browser?attr=value) and observe if the parameter value is reflected in the page without sanitization.Affected if Arbitrary input in the schema-browser parameter is rendered unsanitized in the page output
You are affected if running Apache Solr version 5.2.1 or earlier AND the Admin UI is accessible with the schema-browser functionality exposed to untrusted users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to Apache Solr 5.3 or later to obtain the patched version. Alternatively, implement URL parameter validation/sanitization in the schema-browser.js file or deploy a WAF rule to filter malicious schema-browse URL patterns.
Fix this in Solr
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-8796 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-8796 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data