FitTrackee's small public signal still maps to sensitive activity data
FitTrackee is a self-hosted outdoor activity tracker. It records workouts, routes, timing, and related account data. A small internet-facing population can still carry a meaningful privacy risk because location history and training patterns describe a person's movements.
The count-only ZoomEye observation on 2026-11-16 found 0 matches for app="FitTrackee", 29 for title="FitTrackee", and 79 for http.body="FitTrackee". The queries used sub_type=all, page 1, and pagesize 1. The title count is the most direct of the three signals, but it remains an index observation. It does not prove that a title belongs to a live instance, that accounts are exposed, or that an activity record is readable.
The project's environment example requires a production configuration and a unique JWT_SECRET_KEY. Its Redis dependency is documented for API rate limits, user data export, and email sending. These settings affect different controls. A weak signing key can undermine session integrity. Missing rate limiting can make authentication and API probing cheaper. Missing email configuration can break account recovery or user export.
Inspect authentication and account policy
FitTrackee supports account creation and API clients. The deployment owner should determine whether registration is open, whether email confirmation is required, how password reset works, and which token lifetime applies. Check whether external applications use OAuth clients or user tokens and whether a revoked token stops access immediately.
The JWT signing key should be generated for this deployment, stored outside the web root, and rotated with a plan for existing sessions. Do not reuse a key from an example file or another instance. If an identity provider is placed in front of FitTrackee, verify that the application still knows the authenticated user and does not accept a direct request that bypasses the proxy.
Review the data path
Activity records can include GPX tracks, workout files, public profile data, and social interactions. Define which items are private by default. Review visibility settings for each activity and profile, API responses, RSS or export jobs, and map-tile providers that may receive coordinates. A private dashboard that sends a precise route to an untrusted tile service has not kept the route private.
Redis is part of the operational boundary. If it is reachable from the FitTrackee application only, use a private address and authentication appropriate to the deployment. If the application export queue stores user data, protect it as production data. Do not expose Redis merely because the web front end needs a backend service.
Validate the title candidate
Start from the page title and confirm the product's static assets, API paths, and login page. Check the response headers, redirect chain, certificate, and host ownership. Then ask the owner for an authenticated check of registration policy, administrator accounts, token expiry, and activity visibility.
The 29-title result is not a vulnerability count. It is a scoped list of candidates that deserves a repeatable review. Log the query, observation time, and validation result. If the service is intentional, keep the evidence and the owner. If it is not, remove public reachability before deleting logs that may be needed to understand the exposure.
Top comments (0)