Skip to main content
VulnerabilityPublished

CVE-2025-60291: eTimeTrackLite Web thru · Improper Access Control

Source CVE Database V5

0

Not known to be exploited · CVSS 9.1 Critical.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

  1. Immediately restrict network access to eTimeTrackLite administrative routes using firewalls or web application firewalls (WAFs) to limit exposure to trusted IP addresses only.
  2. Conduct a thorough access control audit on the eTimeTrackLite deployment to ensure proper permission enforcement on all sensitive routes.
  3. Monitor logs and network traffic for unusual access patterns or attempts to reach administrative endpoints without authentication.
  4. Implement network segmentation to isolate the eTimeTrackLite server and its database from other critical infrastructure.
  5. When available, apply official patches or updates from the vendor addressing CVE-2025-60291 without delay.
  6. Consider deploying runtime application self-protection (RASP) or intrusion detection systems (IDS) to detect and block exploitation attempts.
  7. Review and harden database connection configurations to prevent unauthorized changes, including enforcing strong authentication and encryption.
  8. Educate IT and security teams about this vulnerability and incorporate it into incident response plans.
  9. If patching is delayed, consider temporary mitigations such as disabling vulnerable features or using reverse proxies to enforce access controls.

Description

An issue was discovered in eTimeTrackLite Web thru 12.0 (20250704). There is a permission control flaw that allows unauthorized attackers to access specific routes and modify database connection configurations.

References

Community reviews

Loading reviews…