Time ClockWordPress extension · Wpplugin
CVE-2024-9593
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 · uneditedThe Time Clock plugin and Time Clock Pro plugin for WordPress are vulnerable to Remote Code Execution in versions up to, and including, 1.2.2 (for Time Clock) and 1.1.4 (for Time Clock Pro) via the 'etimeclockwp_load_function_callback' function. This allows unauthenticated attackers to execute code on the server. The invoked function's parameters cannot be specified.
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 · moderate confidenceThe Time Clock and Time Clock Pro WordPress plugins contain an unauthenticated Remote Code Execution vulnerability in the 'etimeclockwp_load_function_callback' function affecting versions up to 1.2.2 and 1.1.4 respectively. Attackers can execute arbitrary server-side code without authentication. The note that function parameters cannot be specified may limit exploitation in some scenarios but the core RCE capability remains exploitable.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Time ClockWordPress extension
<= 1.1.4<= 1.2.2CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Check if Time Clock plugin is installedNavigate to WP Admin > Plugins or inspect /wp-content/plugins/ directory for folders containing 'time-clock' in the nameAffected if The plugin folder exists in the WordPress plugins directory
-
Identify the exact plugin version installedIn WordPress admin, go to Plugins > Installed Plugins and find the version number listed under the plugin name, or check the main plugin PHP file for the 'Version' header in the plugin comment blockAffected if The installed version is 1.1.4 or lower for Time Clock, or 1.2.2 or lower for Time Clock Pro
-
Check if the vulnerable endpoint is accessibleSend a request to the endpoint that handles etimeclockwp_load_function_callback - typically this would be via admin-ajax.php or a direct AJAX handler. Inspect the site's AJAX endpoints and look for calls to 'etimeclockwp_load_function' action.Affected if The endpoint responds and accepts the vulnerable parameter without authentication
-
Verify plugin is activeIn WordPress admin > Plugins, confirm the Time Clock or Time Clock Pro plugin shows as 'Active'Affected if The plugin is currently active on the site
If the Time Clock plugin version is 1.1.4 or lower, or Time Clock Pro is 1.2.2 or lower, and the plugin is installed and active, the site is vulnerable to unauthenticated RCE via the etimeclockwp_load_function_callback function.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate to the latest patched versions of the Time Clock and Time Clock Pro plugins immediately. If updates are unavailable, consider removing the plugins until a fix is released, or disable the affected endpoint at the web server level.
Fix this in Time Clock
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9593 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-9593 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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