Dev.to Security πŸ” Cybersecurity πŸ‘ 0 πŸ“– 3 min read

TinaCMS' Nine Title Matches Hide a More Useful Admin Route Question

TinaCMS' Nine Title Matches Hide a More Useful Admin Route Question TinaCMS is a Git-backed content management system that can use TinaCloud or a self-hosted backend. In self-hosted mode, a single API function exposes

TinaCMS' Nine Title Matches Hide a More Useful Admin Route Question

TinaCMS is a Git-backed content management system that can use TinaCloud or a self-hosted backend. In self-hosted mode, a single API function exposes a GraphQL endpoint for content and handles authentication and authorization. The editing interface is normally reached through the site's /admin route.

A ZoomEye query on 2026-11-22 returned 9 matches for title="TinaCMS". app="TinaCMS" returned zero and http.body="TinaCMS" returned 160. The title count is small and the body count includes documentation and source repositories. Neither query proves that the /admin route is reachable or that a backend is self-hosted.

The visible route is not the whole backend

A Tina site may serve a public front end while the data layer runs as a serverless function, a Next.js route handler, or a separate API. The admin HTML can be public because the login redirect happens in the browser, or the site can block the entire route at the proxy. A title match on a marketing site does not answer which design is in use.

Self-hosting changes the responsibility. Tina's overview says the operator chooses the auth provider, database adapter, and Git provider. The default Auth.js provider uses a user collection in the database, and a custom provider can replace it. Each choice creates a credential path and an authorization decision that must be tested.

A public admin route that always redirects to login is not automatically a weakness. It is still useful to inventory because it identifies the CMS, the authentication provider, and the deployment style. The reviewer should follow the redirect and inspect only what is publicly served, without attempting to log in to unknown sites.

Reviewing an owned site

Map the public front end, /admin route, GraphQL endpoint, auth callback, database adapter, and Git integration. Confirm that the backend endpoint is not reachable around the intended proxy path. If the deployment uses serverless functions, verify that the function cannot be invoked from an origin or method that bypasses the auth provider.

Review the auth provider configuration. Check allowed redirect hosts, callback URLs, session cookies, domain restrictions, and the behavior when an OAuth or identity-provider response is incomplete. For a custom provider, verify authorization on every content mutation rather than only at the UI.

Check how the Git provider writes content. A content editor should not be able to rewrite arbitrary branches or workflow files unless that capability is intended. Keep the Git token narrow, rotate it when staff changes, and separate preview or draft writes from production deployment.

Review GraphQL operations for object-level authorization. A CMS often has collections with different visibility and editing roles. A valid user session should not imply access to every collection, path, or branch. Test read, create, update, delete, and publish operations separately.

Building a better query

The title count is too small and too generic to be a population estimate. A better inventory combines an owned domain list with a product-specific admin asset, GraphQL endpoint behavior, and the authentication provider's redirect. For public research, record only the observed page and avoid interacting with the backend.

For each owned deployment, store the site URL, admin URL, backend endpoint, auth provider, database type, Git provider, and owner. Recheck after framework upgrades because a route move can change both the public path and the proxy policy.

TinaCMS can be a secure Git-backed CMS with a small web signature. The security decision is not whether nine titles appear in an index. It is whether the self-hosted backend, admin route, auth provider, and Git credential all agree on who may change content.

References

πŸ“° Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes β€” full credit and traffic to the original publisher.