Ghost CMS fingerprints describe publishing platforms, not their admin trust
Ghost is a publishing platform with a public site, a staff administration area, a Content API, and a private Admin API. The public site is designed to be read. The Admin UI and Admin API can create posts, change settings, manage members, and perform integrations. A broad product fingerprint therefore describes a publishing platform population, not a list of exposed administrator consoles.
On November 20, 2026, ZoomEye returned 42 matches for title="Ghost CMS" and 32,351 for app="Ghost" with sub_type=all, page 1, and pagesize 1. The large difference is a useful lesson in field selection. The application field can identify public Ghost sites that expose very little administrative information. The title string finds a narrower set of pages that use a particular phrase. Neither query establishes that the Admin API is reachable or that an administrator account is weak.
Separate content access from integration authority
Ghost's Content API is intended for public content retrieval and uses a Content API key. The Admin API uses a private Admin API key to sign short-lived JWTs that make changes. The keys are not interchangeable. A public content integration should not be described as administrator access, and an exposed public site should not be treated as proof that the Admin API key has leaked.
Inventory the admin URL, staff accounts, custom integrations, webhook destinations, and API keys. Check whether the Admin API is protected by the identity provider and whether integration keys have an owner and rotation plan. The admin key is a bearer authority for the integration's actions, so storing it in a theme, browser bundle, or public repository destroys the separation.
Review the public and private hostnames
Ghost can run with the same host serving the site and admin paths, or behind a proxy that routes them differently. Verify the redirect, TLS, cookie domain, and authentication behavior for the admin path. Test that the Content API remains read-only and that the Admin API rejects an unsigned or incorrectly signed request.
The proxy configuration matters. A rule that protects /ghost but not /ghost/api leaves an alternate route. A rule that protects the UI but forwards the Admin API without authentication is not a complete boundary. Capture the exact route and the authentication result rather than only status code 200.
Keep the count in perspective
The 32,351 application matches are a large platform population. The 42 title matches are a narrow phrase search. For owned sites, verify version, staff roles, integrations, and backups. For external candidates, stop at public evidence and do not attempt to use an Admin API without authorization.
Ghost's footprint tells us where publishing software appears. The security question is which of those sites has a private administrative path with a key that can publish, delete, or change site settings. That requires identity and configuration evidence beyond a product count.
