Summary
Goobi viewer exposed a REST endpoint that accepted arbitrary Solr streaming expressions from unauthenticated network clients and forwarded them directly to the backend Solr server.
Under these conditions, an attacker on the network could read the entire search index and, in default Solr configurations, modify or delete indexed records without any prior authentication.
Affected context
This vulnerability exists in Goobi viewer deployments using versions from 4.8.0 up to, but not including, 26.04.1 where:
- The
/api/v1/index/streamREST endpoint is reachable over the network - The endpoint is exposed without authentication or access control
- Goobi viewer is connected to a Solr backend that trusts requests from the application
In typical setups, the Solr server assumes that calls from Goobi viewer are trusted and therefore processes the provided streaming expressions with full index access.
Exploit preconditions
- Attack surface: Network-accessible Goobi viewer instances exposing
/api/v1/index/stream - Required access: Any unauthenticated client able to send HTTP POST requests to the endpoint
- Trigger point: Submission of a crafted Solr streaming expression via the vulnerable REST API
- Why exploitation is possible: The endpoint forwards user-supplied streaming expressions to Solr without enforcing authentication, authorization, or expression-level restrictions, effectively granting full backend index capabilities to anonymous users.
Why this happens
The core issue is a missing authentication and authorization check on a high-privilege administrative-like API endpoint that proxies commands to Solr.
By treating all callers of /api/v1/index/stream as trusted, the application violates the principle of least privilege: untrusted network clients gain the same capabilities as the backend application.
This maps to CWE-306: Missing Authentication for Critical Function, where sensitive operations (in this case, index read/write operations via Solr streaming expressions) are exposed without verifying the identity or privileges of the requester.
Potential impact
- An attacker could read the entire contents of the Solr index, including potentially sensitive metadata and document fields.
- An attacker could create, modify, or delete indexed records, leading to data loss or integrity issues.
- Search results could be manipulated to hide, reorder, or highlight certain records (censorship or misinformation).
- Downstream systems that consume search index data could be poisoned with incorrect or malicious entries.
- Operational disruption of search functionality if critical index structures or documents are removed or corrupted.
General mitigation guidance
Mitigation generally focuses on adding strong access control around high-privilege backend endpoints and reducing the trust boundary between the web application and Solr:
- Require authentication and role-based authorization for any endpoint that can execute search engine commands, especially those that support arbitrary expressions or administrative actions.
- Restrict exposed API capabilities to the minimal set required by client-facing functionality; avoid passing through arbitrary backend query languages or scripting primitives.
- Place Solr behind a controlled network boundary so that only trusted application components can communicate with it directly.
- Implement server-side validation and whitelisting of allowable query patterns or streaming expressions to limit backend operations.
- Apply the principle of least privilege to Solr users/cores so that even if an endpoint is misused, write and delete actions are constrained.
How teams detect issues like this
Detection approaches typically combine code-level review with runtime monitoring:
- Static analysis & code review: Identify REST endpoints that:
- Proxy or forward user input directly to backend services (such as Solr)
- Lack explicit authentication/authorization checks before performing critical operations
- Permit arbitrary query or expression strings without validation
- Configuration and policy checks: Enforce policies that:
- Require authentication on all non-public or state-changing endpoints
- Prohibit direct exposure of administrative or index-management functionality to anonymous users
- Runtime monitoring and logging:
- Log use of high-privilege endpoints with caller identity, source IP, and requested expressions
- Monitor for unusual index operations, such as mass deletions, unexpected commit patterns, or large-scale reads from anonymous clients
Automated security testing tools and API gateways can help flag endpoints that violate access control policies or expose dangerous backend operations.

