Anuko Time Tracker's 155 body matches sit behind a group and role hierarchy
Time-tracking systems reveal projects, clients, budgets, and working patterns. Anuko Time Tracker is an open-source PHP application with nested groups and configurable roles. Its exposure cannot be inferred from a generic time-tracker title, so I tested a product-specific page phrase.
On 2026-11-22 at 00:45 UTC, ZoomEye returned 155 matches for http.body="Anuko Time Tracker" and zero for app="Anuko Time Tracker". The query used sub_type=all, page 1, and pagesize=1. These are index counts, not confirmed vulnerable installations.
Open the body-match result in ZoomEye. A body match is more specific than a generic title="Time Tracker" query because it looks for the product name in page content. It still cannot distinguish a live login page from documentation, a copied template, or a demonstration instance.
Groups and ranks define the data boundary
Anuko's documentation describes an organization as a tree of nested groups. Users belong to a group and receive a role with an integer rank. The fixed Administrator role can manage groups and import group data. Editable roles carry access rights such as tracking time, viewing reports, and managing users whose rank is lower than the manager's.
That model is more useful to an exposure review than a single login count. A public login page may be expected for a time-tracking service. The real question is which users can cross group boundaries, which roles can export all reports, and whether the deployment keeps the default admin account or secret password described in the vendor documentation.
The vendor's documentation states that admin is the default Administrator login and secret is the default password. A deployment that still accepts those values has a concrete configuration issue. Do not assume the documented default is active on every host; verify it only on systems you are authorized to test.
Validate body matches before contacting owners
Use the body phrase to build a candidate set, then open a small number of authorized pages and check for the product's login form, asset paths, and session behavior. Pair the HTTP observation with DNS ownership, certificate subject, and organizational asset records.
For confirmed deployments, review group inheritance, role ranks, plugin settings, and report access. Check whether client roles can see unapproved entries, whether one group can import another group's data, and whether PDF or custom-plugin features expose uploads beyond the intended users.
Review account lifecycle separately. A former contractor with a login can remain inside a group after the project ends. The administrator should compare the user list with the current client and staffing list, then remove stale accounts and rotate any shared API credentials. The time tracker's role hierarchy is only a control if the membership data is current.
Treat the count as a lead, not a leak report
The 155 body matches can include documentation mirrors and hosted demonstrations. The zero application count does not mean there are no deployments; it means ZoomEye did not assign the product fingerprint in the fields queried. A body phrase and an application fingerprint measure different evidence.
Use repeated measurements to detect changes in the candidate population, but keep the ownership check inside the workflow. A stable count over time is not a safety certificate. A rising count is not proof of unauthorized use.
The useful outcome is an inventory of confirmed instances by group and role, with default-credential checks, report-export review, and current account membership. The product-specific body query gives a manageable starting point for that work.
Top comments (0)