dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-9018

HIGH · 8.8 CVSS v3.1 Published 2025-09-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
The Time Tracker plugin for WordPress is vulnerable to unauthorized modification and loss of data due to a missing capability check on the 'tt_update_table_function' and 'tt_delete_record_function' functions in all versions up to, and including, 3.1.0. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update options such as user registration and default role, allowing anyone to register as an Administrator, and to delete limited data from the database.

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

The Time Tracker WordPress plugin lacks capability checks on the tt_update_table_function and tt_delete_record_function functions, allowing any authenticated user with Subscriber-level access to call these functions. Attackers can modify WordPress options including user registration settings and default user role, enabling anyone to register as Administrator, and can delete limited data from the database.

MitigationUpdate the Time Tracker plugin to version 3.1.1 or later which includes proper capability checks. Alternatively, implement current_user_can() checks on the vulnerable functions before executing database operations.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Verify Time Tracker plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'Time Tracker' in the plugin list. Confirm the plugin is active (check if the 'Activate' or 'Deactivate' link reads 'Deactivate').
    Affected if The Time Tracker plugin is installed and active.
  2. Check installed version number
    In the Plugins list, locate the Time Tracker plugin. The version number is displayed beneath the plugin name. Compare this version to the affected range (any version up to and including 3.1.0).
    Affected if The installed version is 3.1.0 or lower.
  3. Confirm vulnerable AJAX endpoints exist
    Access the site via FTP or file manager. Navigate to wp-content/plugins/time-tracker/ and locate the AJAX handler files (typically ajax文件夹 or functions that register tt_update_table_function and tt_delete_record_function). Search for these function names in the plugin PHP files.
    Affected if The functions tt_update_table_function and tt_delete_record_function are present without proper capability checks (current_user_check or similar).
  4. Identify if subscriber-level access exists
    In WordPress admin, go to Users > All Users. Review the user roles column. Check if any accounts have 'Subscriber' role, or if WordPress user registration is enabled (Settings > General > 'Membership: Anyone can register' is checked).
    Affected if There are subscriber-level user accounts OR open user registration is enabled, allowing new subscribers to be created.

Your environment is affected if the Time Tracker plugin versions 3.1.0 or lower are installed and active, and any subscriber-level user account can exist or be created.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Time Tracker plugin to version 3.1.1 or later which includes proper capability checks. Alternatively, implement current_user_can() checks on the vulnerable functions before executing database operations.

Recommended fix High confidence

Time Tracker plugin version 3.1.1 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find the 'Time Tracker' plugin
  4. Check if the current version is 3.1.0 or lower
  5. If vulnerable, click 'Update Now' to update to the latest version
  6. Alternatively, download the latest version from wordpress.org/plugins/time-tracker and upload via Plugins > Add New > Upload Plugin
  7. After update, verify the version number reflects the patched release

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-9018 — 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-9018 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