Vulnerability report

Exploited in the wild High confidence Not in CISA KEV

CVE-2024-9593

Time Clock Pro Remote Code Execution

Scott Paterson / Time Clock Pro · 0 to <= 1.2.2

Severity
CVSS 8.3 · High
Confidence
High
Exploit status
Exploited in the wild
EPSS
12.4%
First observed
—
Last observed
—

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2024-9593 is an unauthenticated vulnerability affecting Scott Paterson Time Clock Pro, Time Clock – A WordPress Employee & Volunteer Time Clock.... The Time Clock plugin and Time Clock Pro plugin for WordPress are...

Is it exploited?

Yes. Previdian tracks this CVE as a known exploited vulnerability. Confidence is high. Also confirmed by third-party sources.

Who is affected?

Scott Paterson / Time Clock Pro 0 to <= 1.2.2.

What should we do?

Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.

Overview

Time Clock Pro Remote Code Execution

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.

wpplugin Affected
time_clock
Through 1.2.2
wpplugin Affected
time_clock_pro
Through 1.1.4
Scott Paterson Affected
Time Clock Pro
Through 1.1.4
scottpaterson Affected
Time Clock – A WordPress Employee & Volunteer Time Clock Plugin
Through 1.2.2
Published
18 Oct 2024
Exploitation Reported
18 Oct 2024
Attack vector
Remote
Complexity
Low
Privileges
None
User interaction
None

Tags

nuclei_scanner

CVE References

Exploitation evidence

Why Previdian marks this CVE as exploited

Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.

Exploited in the wild

The Shadowserver

Recorded 18 Oct 2024

A trusted third party reported exploitation.

Proof of concept available

Nuclei Templates

Recorded 12 Jun 2026

Public scanner or PoC coverage increases practical exploitability.

Known exploited vulnerability sources

Per-source evidence links for KEV attestations are available through the Previdian Pro API.

Learn about Pro API access
Source Added
The Shadowserver First 2024-10-18 17:32 UTC

Detection

Operational artifacts and observed signals

Make the evidence actionable in scanner, SOC, and edge-control workflows.

Observed signals

Request targets
User-Agents
Callback hosts
0
0
0

Request targets and User-Agents available in Pro. Callback host details available in Enterprise.

Virtual patch status

No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.

Learn about virtual patches →

Scanner Artifacts

Scanner and exploit-framework references linked to this CVE.

Risk and context

Severity, weaknesses, and research context

CVSS v3.1

8.3 High

Potential damage if exploited. Separate from whether attackers are using it.

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

EPSS

12.4%

Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.

Potential Proof of Concepts

These PoCs are unverified and could contain malware. Use at your own risk.

Timeline

From disclosure to observed exploitation

  1. 14:20 UTC

    Public PoC available

    Public proof-of-concept code published

  2. 00:00 UTC

    Nuclei template available

    Scanner coverage available

  3. 17:32 UTC

    CVE published

    Vulnerability disclosed publicly

  4. 17:32 UTC

    Added to Previdian KEV Feed

    High-confidence, third-party attested exploitation

  5. 16:39 UTC

    CVE ID reserved

    Identifier reserved by the CNA

Pro API

Automate this intelligence

Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.

  • Evidence confidence and provenance
  • First-party sensor telemetry
  • PoC and scanner references
  • Affected versions and enrichment
  • Automation-ready JSON delivery

GET /api/v2/pro/kevs/CVE-2024-9593

Sample API response
{
  "cve_id": "CVE-2024-9593",
  "confidence": "High",
  "cvss_score": 8.3,
  "cvss_estimated": false,
  "epss_score": 0.12411,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": false
  },
  "sensor_telemetry": { "attempts": 0, "sensors": 0 }
}