Stump sessions and OPDS credentials protect different parts of a library
Stump is a self-hosted comics, manga, and digital-book server with a web reader and OPDS support. The product has several authentication paths: server-side sessions for the main app, Basic authentication on OPDS endpoints, OIDC support, and API keys gated by a user permission. A simple title count cannot tell which path a deployment uses.
The ZoomEye count-only queries on 2026-11-16 found 0 app matches, 1 match for title="Stump" && http.body="comics", and 25,087 for http.body="Stump". The generic body term is too broad to treat as product evidence. The conditional title and body query is narrower, but one match is still only a candidate.
The official API documentation states that Stump uses server-side sessions stored in the database and cleans expired sessions on a short interval. Basic authentication is limited to OPDS endpoints and is not accepted on the REST API. API keys are available only to users with the ACCESS_API_KEYS permission. Kobo sync is gated by separate permissions. Those distinctions should appear in the inventory.
Test the reader and the catalog
The web reader, REST API, OPDS catalog, and device-sync paths can expose the same books through different handlers. Verify authentication on each path with the owner's authorization. Check that a user with access to one library cannot enumerate another library, download a file outside it, or change reading progress for another account.
OPDS clients often store the Basic-auth credential for a long time. A password change or session revocation should have a defined effect on the catalog. If API keys are used, record the owner, permission set, creation time, last use, and revocation path. A key that is limited to a device should not become an administrator credential after an upgrade.
Validate OIDC and session behavior
If OIDC is enabled, confirm the issuer, callback URL, client secret storage, and custom CA settings. Verify that the application creates a local session only after validating the ID Token and that a session does not survive an account disablement longer than policy allows. Review administrator access separately from reader access.
The database contains session records, library metadata, and reading progress. Protect database backups as identity material because a session table may contain active session identifiers. Encrypt backups, limit restoration access, and remove expired sessions promptly. Do not log API keys, OIDC secrets, or session cookies during troubleshooting.
Review the one-match signal
The conditional query is designed to reduce false positives from the common word Stump. It still does not prove a live deployment or a particular security state. Open the page safely, verify assets and the login route, then ask the owner to confirm the version, libraries, authentication methods, OIDC configuration, and device permissions.
Record the exact dork, count, scope, time, and page evidence. The result is useful as a narrowly scoped lead, not as a population estimate. The deployment review should answer which readers, API clients, sync services, and administrator consoles can reach the content.