SolrApplication · Apache
CVE-2015-8797
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/plugins.js in the stats page in the Admin UI in Apache Solr before 5.3.1 allows remote attackers to inject arbitrary web script or HTML via the entry parameter to a plugins/cache URI.
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 stats page (webapp/web/js/scripts/plugins.js) allows remote attackers to inject arbitrary web script or HTML via the entry parameter to plugins/cache URI. This is a reflected XSS in the Solr web interface affecting versions before 5.3.1.
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.3CVSS 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 the installed Apache Solr versionCheck the Solr server version via the Admin UI at /solr/admin/info/system or check the VERSION.txt file in the Solr installation directory. If running Solr as a service, use the provided version command or check the package metadata.Affected if The version is 5.3 or any version earlier than 5.3.1 (e.g., 5.2.x, 5.1.x, 5.0.x, 4.x series).
-
Verify the Solr Admin UI is accessibleConfirm the Solr Admin UI is reachable over HTTP/HTTPS by accessing the main Admin page (typically at /solr/ or /admin/). Check if network access is allowed to the Admin interface.Affected if The Admin UI is exposed and accessible to users or attackers who can reach the Solr server.
-
Check if the vulnerable plugins/cache endpoint accepts the entry parameterAccess the plugins/cache URI with a test entry parameter value. For example: /solr/plugins/cache?entry=test. Observe whether the value provided in the entry parameter is reflected back in the response without proper HTML encoding.Affected if The entry parameter value is reflected directly in the HTML response without sanitization, indicating the vulnerability is present.
-
Confirm the stats page is available in the Admin UINavigate to the stats page within the Solr Admin UI (typically under the Plugins/Stats section). Check if the plugins.js file is being served from the webapp/web/js/scripts/ path.Affected if The stats page loads and the plugins.js script is present and served by the Admin UI, meaning the XSS vector exists.
A user is affected if they are running Apache Solr version 5.3 or earlier with the Admin UI accessible and the entry parameter to the plugins/cache endpoint reflects user input without sanitization.
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.1 or later to obtain the patched version of plugins.js that properly sanitizes the entry parameter.
Fix this in Solr
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-8797 — 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-8797 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