Loading vulnerability…
CVE-2024-9593 is a remote code execution vulnerability in the Time Clock and Time Clock Pro plugins for WordPress, affecting versions up to and including 1.2.2 (Time Clock) and 1.1.4 (Time Clock Pro). The vulnerability exists in the 'etimeclockwp_load_function_callback' function, which can be exploited by unauthenticated attackers to execute arbitrary code on the server. The attack does not require authentication, and the parameters to the invoked function cannot be specified by the attacker.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (2 hidden).
This repository contains a Python exploit script (CVE-2024-9593.py) and a README.md. The exploit targets a remote code execution vulnerability in the Time Clock and Time Clock Pro plugins for WordPress (up to versions 1.2.2 and 1.1.4, respectively). The script first checks if the target site is running a vulnerable version by fetching the plugin's readme.txt file and parsing the 'Stable tag' version. If vulnerable, it sends a POST request to the /wp-admin/admin-ajax.php endpoint with the 'action=etimeclockwp_load_function' parameter, attempting to execute a specified PHP function or file path (default: phpinfo). The results are logged to Nxploit.txt. The exploit is unauthenticated and leverages a network attack vector. The repository is straightforward, with clear separation between detection and exploitation logic, and is intended for operational use against vulnerable WordPress installations.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.