Ghostfolio inventory starts with access, portfolio visibility, and proxy trust
Ghostfolio is a self-hosted wealth-management application. Its public value is a consolidated view of accounts, positions, and performance. The security question is who can see that view, which authentication path produced the session, and whether the application is interpreting proxy headers from a trusted source.
A count-only ZoomEye observation on 2026-11-16 found 0 matches for app="Ghostfolio", 110 for title="Ghostfolio", and 11,205 for http.body="Ghostfolio". The queries used sub_type=all, page 1, and pagesize 1. The body result includes documentation, repositories, mentions, and unrelated pages, so it is not an instance count. The title result is a narrower inventory signal, while the zero application fingerprint means product discovery must use page and response validation.
The official README documents three access paths that matter during review: local email and password authentication, optional security-token access, and an experimental OpenID Connect mode. It also exposes TRUST_PROXY and an optional security-headers feature. Those are separate controls. Enabling OIDC does not remove local accounts unless the deployment does so. A security token is a credential for an API path and needs the same ownership and revocation review as a user account.
Validate the proxy boundary
Ghostfolio can run behind a reverse proxy. The TRUST_PROXY setting tells the application which proxy hops may supply client-address information. Set it to the actual path, not an unrestricted value. A misconfigured trust boundary can let a direct client influence rate limiting, audit logs, or redirect decisions. Verify the application is reachable only through the intended proxy and that the proxy removes untrusted forwarding headers.
The README makes HTTP security headers optional. A public deployment should enable the feature or apply equivalent headers at the edge, then inspect the response through the same hostname users visit. Test content security policy, frame restrictions, referrer policy, and transport security after login and on API responses. A header present on the marketing page and absent from the authenticated application does not protect the portfolio view.
Review identity and data scope
Inventory every enabled user, security token, OIDC issuer, callback URL, and trusted proxy. For OIDC, check issuer discovery, client secret storage, callback registration, and the scope requested. For local authentication, check account creation, password reset, session lifetime, and administrator recovery. For tokens, record purpose, owner, creation time, and last use.
The application holds financial data and may receive external market data. Separate read access to a dashboard from the ability to change accounts, import transactions, or manage users. If the deployment uses multiple users, verify that portfolio and account boundaries are enforced by the application, not only by separate browser tabs.
Turn a title hit into evidence
A title match should lead to a safe GET of the root page, followed by an authenticated check performed by the owner. Record the final URL, response title, headers, application assets, version evidence, authentication mode, and whether registration is open. Do not submit credentials or attempt access to another organization's instance.
The 110-title observation is useful for finding candidates. It cannot show which candidates are live Ghostfolio deployments, which are protected, or which contain sensitive financial records. Inventory quality depends on confirming the product marker, the auth configuration, and the owner. Those checks also produce the evidence needed to fix the boundary when the service was exposed by mistake.
Top comments (0)