All in One Time Clock Lite – Tracking Employee Time Has Never Been Easier <= 2.0 - Insecure Direct Object Reference to Authenticated (Subscriber+) Arbitrary Clocking In/Out
Strategic Overview
- Status
- Patched in 2.0.1
- Affected Version
<= 2.0- CVSS
- 4.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2025-6833
At a glance
CVE-2025-6833 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the All in One Time Clock Lite WordPress plugin, affecting versions <= 2.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.0.1; sites on affected versions should update now. Disclosed October 2025, reported by Jonas Benjamin Friedli.
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-639: Authorization Bypass Through User-Controlled Key
All in One Time Clock Lite <= 2.0 carries this weakness at aio_time_clock_lite_js, and reaching it takes an account at Subscriber level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For All in One Time Clock Lite the fix is 2.0.1: builds <= 2.0 are affected, anything from 2.0.1 onward is not.
Remediation
Update to version 2.0.1, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: All in One Time Clock Lite 2.0.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in All in One Time Clock Lite – Tracking Employee Time Has Never Been Easier
- 6.5CVE-2025-11758: All in One… Page Creation and Information Exposure
CVE-2025-11758 - 6.1CVE-2025-6832: All in One Time Clock Lite Reflected XSS
CVE-2025-6832 - 5.5CVE-2022-44594: All in One Time Clok Lite <= 1.3.320 Stored XSS
CVE-2022-44594 - 4.3CVE-2025-46513: All in One Time Clock Lite <= 1.3.325 CSRF
CVE-2025-46513
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C