CVE-2026-110728: The AIKTP plugin for WordPress is vulnerable to Authorization Bypass via Predictable Token in all
Source GCVE Database
Not known to be exploited · CVSS 5.3 Medium.
Data as of 19 Nov 2026, 13:34 UTC
Thin evidence
One scorer or none| CNA (Wordfence) | CVSS 3.1 | 5.3 |
|---|
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 19 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 18 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| aiktpAIKTP | Affected
| Fixed in– |
Description
The AIKTP plugin for WordPress is vulnerable to Authorization Bypass via Predictable Token in all versions up to, and including, 5.0.7. The vulnerability exists because the plugin's sync token (`aiktpz_token`) is generated using PHP's non-cryptographic `uniqid()` function — producing a wall-clock-derived value with approximately one million microsecond candidates per uncertain generation second — while the unauthenticated, unthrottled REST endpoint `/wp-json/aiktp/checkToken` (registered with `permission_callback => __return_true`) acts as a public brute-force oracle for the token; simultaneously, the capability checks in `check_valid_token` and its wrappers (`verify_aiktp_token_with_edit_capability`, `verify_aiktp_token_with_upload_capability`) inspect only a server-side stored Administrator account (option `aiktp_author`) rather than the actual REST caller, meaning possession of the token alone grants Administrator-equivalent authority to any external request. This makes it possible for unauthenticated attackers to recover the sync token and then invoke `POST /wp-json/aiktp/createpost` to publish arbitrary posts attributed to a site Administrator, `POST /wp-json/aiktp/doUpdatePostWithImageURL` to overwrite the body content of any existing post, and `POST /wp-json/aiktp/doUploadImageToWP` to import remote media and attach it as the featured image of any post. Additionally, when the `aiktpz_token` option has never been initialized, the `checkToken` oracle returns success for an empty token submission due to a loose comparison in `check_valid_token`, providing a zero-effort bypass that requires no brute-forcing whatsoever.
References
- nvd.nist.gov/vuln/detail/CVE-2026-110728 (opens in a new tab)
- plugins.trac.wordpress.org/browser/aiktp/trunk/aiktp.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/aiktp/trunk/aiktp.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/aiktp/trunk/includes/aiktp-sync.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/aiktp/trunk/includes/aiktp-sync.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/aiktp/trunk/includes/aiktp-sync.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/aiktp/trunk/includes/aiktp-sync.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/aiktp/trunk/includes/aiktp-sync.php (opens in a new tab)
- wordfence.com/threat-intel/vulnerabilities/id/916ff9fa-04d1-4d15-92dd-905dd6fe259e?source=cve (opens in a new tab)