All in One Time Clock Lite – Tracking Employee Time Has Never Been Easier <= 2.0.3 - Missing Authorization to Page Creation and Information Exposure
Strategic Overview
- Status
- Patched in 2.0.4
- Affected Version
<= 2.0.3- CVSS
- 6.5Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-11758
At a glance
CVE-2025-11758 is a medium-severity Missing Authorization vulnerability in the All in One Time Clock Lite WordPress plugin, affecting versions <= 2.0.3. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.0.4; sites on affected versions should update now. Disclosed November 2025, reported by Athiwat Tiprasaharn (Jitlada).
Vulnerability Overview
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).
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 privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
Reaching this weakness in All in One Time Clock Lite <= 2.0.3 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For All in One Time Clock Lite the fix is 2.0.4: builds <= 2.0.3 are affected, anything from 2.0.4 onward is not.
Remediation
Update to version 2.0.4, 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.4 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
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C