dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-1094

HIGH · 7.3 CVSS v3.1 Published 2024-06-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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
The Timetics- AI-powered Appointment Booking with Visual Seat Plan and ultimate Calendar Scheduling plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the make_staff() function in all versions up to, and including, 1.0.21. This makes it possible for unauthenticated attackers to grant users staff permissions. CVE-2024-37427 is likely a duplicate of this issue.

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 Timetics WordPress plugin has a broken access control vulnerability where the make_staff() function lacks a capability check, allowing unauthenticated attackers to arbitrarily grant staff permissions to users. This is a privilege escalation issue with CVSS 7.3, affecting all versions up to 1.0.21.

MitigationUpdate to version 1.0.22 or later which includes proper capability verification before executing the make_staff() function. Until then, consider disabling the plugin or implementing WAF rules to block unauthorized staff permission requests.

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
Low
Integrity
Low
Availability
Low

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

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 Timetics plugin is installed
    Navigate to WordPress admin dashboard > Plugins, or inspect wp-content/plugins/timetics/ directory via file manager/SSH. Locate the main plugin file (timetics.php) and check the version header comment.
    Affected if The Timetics plugin is present on the WordPress site.
  2. Identify installed Timetics version
    Open the main Timetics plugin file and locate the 'Version:' field in the plugin header comment, or check the readme.txt file for the version number.
    Affected if The installed version is 1.0.21 or lower (all versions up to 1.0.21 are affected).
  3. Verify make_staff function accessibility
    Inspect the Timetics plugin source code, specifically searching for the make_staff() function definition. Check if it contains a current_user_can() or similar capability check before executing. Look for AJAX hooks or direct action handlers that call this function.
    Affected if The make_staff() function lacks a capability check and is accessible without authentication (no require_login, no nonce verification, or no current_user_can() call).
  4. Inspect for unauthorized staff accounts
    Query the WordPress database: SELECT * FROM wp_usermeta WHERE meta_key LIKE '%timetics%' or '%staff%'; Alternatively, check the WordPress admin under Timetics settings for any staff accounts you did not create.
    Affected if There are staff user accounts present that were not created by legitimate administrators.
  5. Review access logs for suspicious requests
    Examine web server access logs (Apache/Nginx) for POST requests to admin-ajax.php or direct Timetics endpoints containing action parameters like 'make_staff', 'add_staff', or similar.
    Affected if There are unauthenticated POST requests to staff-related actions in the logs.

You are affected if the Timetics plugin version is 1.0.21 or lower AND the make_staff function is exposed without authentication, allowing any visitor to escalate privileges to staff member.

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 to version 1.0.22 or later which includes proper capability verification before executing the make_staff() function. Until then, consider disabling the plugin or implementing WAF rules to block unauthorized staff permission requests.

Recommended fix Moderate confidence

Timetics plugin version 1.0.22 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Timetics plugin
  4. Check if the current version is 1.0.21 or below
  5. If vulnerable, click 'Update Now' to install the latest version
  6. After updating, verify the new version number confirms the update was successful
  7. Test that the staff permissions functionality works correctly with proper authorization checks in place

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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