Skip to content
Laskyr

Plugins · aio-time-clock-lite · data as of 2026-11-04

Is All in One Time Clock Lite safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (2.1.0)

As of 2026-11-04. 5 issues are on record for older versions; version 2.0.4 or newer fixes all of them that state a fix.

Latest version
2.1.0
Last updated
2026-08-23
Active installs
500+
Known issues on record
5
Unpatched in latest
0
Tested up to WP
7.1.4 · PHP 7.1+

Employees can easily clock in and out. Managers can run reports, keep track of employees/volunteers/contractors and their time. — by Codebangers

What to do

  1. Update to the latest version (2.1.0). Anything older than 2.0.4 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
  2. If you cannot update right away, deactivate it until you can.
  3. Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
  4. If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get aio-time-clock-lite --field=version shows what you run; wp plugin update aio-time-clock-lite updates it.

Check your version

Known vulnerabilities

5 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

medium 6.5 CVE-2025-11758 · published 2025-11-04

Missing authorization check in All in One Time Clock Lite (2.0.3 and older)

Affected
2.0.3 and older
Fixed in
2.0.4 *
Access needed (per CVSS)
No login needed
Range from
CVE record (the advisory publisher) · score by Wordfence
Details from the advisory

The All in One Time Clock Lite plugin for WordPress is vulnerable to unauthorized access due to a missing authorization check in all versions up to, and including, 2.0.3. This is due to the plugin exposing admin-level AJAX actions to unauthenticated users via wp_ajax_nopriv_ hooks, while relying only on a nonce check without capability checks. This makes it possible for unauthenticated attackers to create published pages, create shift records with integrity issues, and download time reports containing PII (employee names and work schedules).

NVD CVE-2025-11758Wordfence advisoryCode change (fix)Plugin source

medium 4.3 CVE-2025-6833 · published 2025-10-22

Missing authorization check in All in One Time Clock Lite (2.0 and older)

Affected
2.0 and older
Fixed in
2.0.1 *
Access needed (per CVSS)
Needs a low-level account (e.g. subscriber)
Range from
CVE record (the advisory publisher) · score by Wordfence
Details from the advisory

The All in One Time Clock Lite – Tracking Employee Time Has Never Been Easier plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.0 via the 'aio_time_clock_lite_js' AJAX action due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with subscriber access and above, to clock other users in and out.

NVD CVE-2025-6833Wordfence advisoryCode change (fix)

medium 6.1 CVE-2025-6832 · published 2025-08-02

Reflected cross-site scripting (XSS) in All in One Time Clock Lite (2.0 and older)

Affected
2.0 and older
Fixed in
2.0.1 *
Access needed (per CVSS)
No login needed; someone on the site has to click a link or open a page
Range from
CVE record (the advisory publisher) · score by Wordfence
Details from the advisory

The All in One Time Clock Lite – Tracking Employee Time Has Never Been Easier plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'nonce' parameter in all versions up to, and including, 2.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

NVD CVE-2025-6832Wordfence advisoryCode change (fix)

medium 4.3 CVE-2025-46513 · published 2025-04-24

Cross-site request forgery (CSRF) in All in One Time Clock Lite (1.3.326 and older)

Affected
1.3.326 and older
Fixed in
1.3.326
Access needed (per CVSS)
No login needed; someone on the site has to click a link or open a page
Range from
CVE record (the advisory publisher) · score by Patchstack
Details from the advisory

Cross-Site Request Forgery (CSRF) vulnerability in Codebangers All in One Time Clock Lite aio-time-clock-lite allows Cross Site Request Forgery.This issue affects All in One Time Clock Lite: from n/a through < 1.3.326.

NVD CVE-2025-46513Patchstack advisory

medium 4.8 CVE-2022-44594 · published 2023-04-23

Stored cross-site scripting (XSS) in All in One Time Clock Lite (1.3.320 and older)

Affected
1.3.320 and older
Fixed in
1.3.321
Access needed (per CVSS)
Needs an admin-level account; someone on the site has to click a link or open a page
Range from
CVE record (the advisory publisher) · score by NVD
Details from the advisory

Auth. (admin+) Stored Cross-Site Scripting (XSS) vulnerability in Codebangers All in One Time Clock Lite plugin <= 1.3.320 versions.

NVD CVE-2022-44594Patchstack advisory

Recent activity

Browse vulnerabilities

Where this data comes from

Badge for your site or docs (states facts with a date, not a verdict):
All in One Time Clock Lite vulnerability status badge
<a href="https://laskyr.com/plugins/aio-time-clock-lite"><img src="https://laskyr.com/plugins/aio-time-clock-lite/badge.svg" alt="All in One Time Clock Lite vulnerability status"></a>

← Check another plugin · Free hacked-site scan

First hour checklist

If the site was just hacked, read the emergency kit before you delete files. The page is free. Email is optional.

Read the emergency kit