WordPress plugin · time-clock
Is Time Clock safe?
Safe on 1.3.2 or newer.
The current version, 1.3.2, is past every affected range on record (3 of 3 records list one). Keep it updated and you’re clear of them.
- Flaws on record
- 3
- High or critical
- 1
- Exploited
- none
- Current version
- 1.3.2
- Last updated
- Aug 22, 2026
- Active installs
- 500+
Every recorded flaw
- Oct 24, 2025Time Clock – A WordPress Employee & Volunteer Time Clock: Stored Cross-Site ScriptingCVE-2025-10701 · affects up to 1.3.1 · reported by WordfenceMedium 6.4
- May 7, 2025Time Clock: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')CVE-2025-47516 · affects up to 1.2.3 · reported by PatchstackMedium 5.9
- Oct 18, 2024The 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) aCVE-2024-9593 · affects up to 1.2.2 · reported by Wordfence12% oddsHigh 8.3
Records come from the National Vulnerability Database, published by the researchers who found each flaw (Wordfence, Patchstack, WPScan and others); exploited status from CISA; exploit odds from FIRST’s EPSS; current version, installs and closures from wordpress.org, checked daily. Want every plugin on your site checked at once? Run the free website check.
Weekly security brief
The flaws that hit local websites, every Friday.
One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.
Tell us what you're building.
A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.
Not ready to talk yet? Run the free website check and see what Google sees.