The Clockinator Lite WordPress plugin before 1.1.0 does not restrict access to several of its record deletion actions
Source GCVE Database
Not known to be exploited : upgrade to 1.1.0 soon.
Data as of 12 Nov 2026, 07:05 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 1.1.0
Exploitation evidence
Disclosed: evidence found.
CVE published 12 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
Upgrade Clockinator Lite (WordPress plugin) to 1.1.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Clockinator Lite | Affected
| Fixed in
|
AI-suggested
A fixed version 1.1.0 of the Clockinator Lite WordPress plugin is available that addresses these vulnerabilities. Users should upgrade to version 1.1.0 or later to remediate the issue. No additional mitigation steps are indicated in the available data.
Description
The Clockinator Lite WordPress plugin versions prior to 1.1.0 contain vulnerabilities that allow unauthenticated users to perform SQL injection attacks. These vulnerabilities stem from insufficient access restrictions on record deletion actions and the use of user-supplied table names in SQL queries without proper validation or escaping. Exploitation can lead to deletion of data from any database table and extraction of sensitive information such as password hashes.