Security Resilience

CVE-2024-9593

Wpplugin Time Clock ≤ 1.1.4

Published
18 October 2024
Modified
29 October 2024
Patch / advisory
CVSS Score v3.1 8.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L
EPSS Score 0.12 96th percentile
Risk Priority 86 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-9593 is a high-severity Code Injection (CWE-94) vulnerability in Wpplugin Time Clock. Its CVSS base score is 8.3 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 4% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

The Time Clock and Time Clock Pro plugins for WordPress are vulnerable to remote code execution in versions through 1.2.2 and 1.1.4 respectively. The flaw resides in the etimeclockwp_load_function_callback function, which permits invocation of arbitrary server-side functions and is tracked as CWE-94. The issue carries a CVSS 3.1 score of 8.3 with a network attack vector, no required privileges or user interaction, and changed scope.

Unauthenticated remote attackers can trigger the callback to execute code on the hosting server. Although the attacker cannot supply parameters to the invoked function, successful exploitation still allows limited control over confidentiality, integrity, and availability within the affected WordPress installation.

Public references from Wordfence and the WordPress plugin repository document the vulnerable code path and include changeset 3171046 that addresses the issue in subsequent releases. The current EPSS of 0.8550 indicates substantial exploitation interest following disclosure.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

The 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…

more

attackers to execute code on the server. The invoked function's parameters cannot be specified.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1059.001 PowerShell Execution
Adversaries may abuse PowerShell commands and scripts for execution.
T1059.003 Windows Command Shell Execution
Adversaries may abuse the Windows command shell for execution.
T1059.004 Unix Shell Execution
Adversaries may abuse Unix shell commands and scripts for execution.
T1059.006 Python Execution
Adversaries may abuse Python commands and scripts for execution.
T1059.007 JavaScript Execution
Adversaries may abuse various implementations of JavaScript for execution.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-50492Same vendor: Wpplugin
CVE-2023-29963Shared CWE-94
CVE-2026-73268Shared CWE-94
CVE-2025-64691Shared CWE-94
CVE-2023-29492Shared CWE-94
CVE-2026-33608Shared CWE-94
CVE-2024-48700Shared CWE-94
CVE-2023-44853Shared CWE-94
CVE-2018-25357Shared CWE-94
CVE-2026-27674Shared CWE-94

Affected Assets

wpplugin
time clock
≤ 1.1.4 · ≤ 1.2.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.3.1

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation finds code paths that accept and execute externally influenced strings.

Input validation directly stops untrusted data from being used to construct executable code without neutralization.

Least privilege limits the damage an injected code fragment can perform once executed.

Requiring documented secure development standards and tools enforces use of safe code-generation APIs and escaping.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
blocks

PR.PS-06's SDLC practices directly target injection flaws via secure coding and testing (mostly), yet as a single broad outcome it leaves many code-generation specifics unaddressed (partial).

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Banning unapproved code samples and unauthenticated web services, combined with secure-coding standards and SAST, prevents the dynamic generation or inclusion of attacker-supplied code.

References