Skip to main content
CVE-2024-9593VulnerabilityPublished Updated

CVE-2024-9593: Time Clock Pro (WordPress plugin) · Code Injection

Affects Time Clock Pro (WordPress plugin)Source CVE Database V5

0

Not known to be exploited · public detection template (Nuclei) · 12% EPSS · CVSS 8.3 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
8.3High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
12.4% chance of exploitation in 30 days – higher than 96% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Oct 2024

  2. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
Scott Paterson Time Clock ProAffected
  • =0
Fixed in–

AI-suggested

Until a patch is available, consider disabling or removing the affected plugins if possible. Monitor official Scott Paterson or WordPress plugin repositories for updates addressing this vulnerability.

Description

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 attackers to execute code on the server. The invoked function's parameters cannot be specified.

References

Community reviews

Loading reviews…