dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2025-60291

CRITICAL · 9.1 CVSS v3.1 Published 2025-10-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

eTimeTrackLite Web through version 12.0 contains a broken access control vulnerability that allows unauthenticated attackers to access specific administrative routes and modify database connection configurations. This permission control flaw enables attackers to potentially alter database credentials or connection strings, leading to data breach or system compromise.

MitigationImplement proper authentication and authorization checks on all sensitive routes, particularly those handling database configuration. Restrict access to administrative functions and validate user permissions before allowing any configuration changes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm eTimeTrackLite Web installation
    Check for eTimeTrackLite Web application files in the web root directory, typically found in paths like /webapps/etimetracklite, /inetpub/etimetracklite, or the application server's web directory. Look for common eTimeTrackLite artifacts such as timetrack.aspx, default.aspx, or configuration folders.
    Affected if eTimeTrackLite Web is present on the server
  2. Identify installed version
    Locate the version file or assembly information. Common locations include: version.txt, about.aspx, the web.config file, or the bin directory DLL properties. Check the footer or login page HTML source for version information.
    Affected if Installed version is 12.0 or any version prior to 12.0
  3. Identify exposed administrative routes
    Access the application and attempt to reach common administrative paths such as /admin, /settings, /Configuration, /dbconfig, /ConnectionString, or paths containing 'config' in the URL without providing any credentials. Use a browser or curl to make unauthenticated requests.
    Affected if Administrative or configuration pages are accessible without authentication (HTTP 200 response instead of redirect to login)
  4. Verify database configuration endpoints
    Test specific endpoints that handle database connection settings. Common paths include: /Config/DBConnection, /Settings/Database, /admin/dbsettings, or similar URL patterns. Submit requests without any authentication headers or session cookies.
    Affected if Database configuration endpoints return sensitive information or accept changes without authentication
  5. Check access control enforcement
    Review web.config or application configuration files for URL authorization rules. Look for <authorization> elements and ensure <allow> rules explicitly restrict access to authenticated users only. Verify that <deny users="?"> is properly configured.
    Affected if Authorization rules are missing, misconfigured, or allow anonymous access to sensitive paths

The environment is affected if eTimeTrackLite Web version 12.0 or earlier is installed AND administrative or database configuration routes are accessible without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authentication and authorization checks on all sensitive routes, particularly those handling database configuration. Restrict access to administrative functions and validate user permissions before allowing any configuration changes.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-60291 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-60291 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data