CVE-2026-110728 Details
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.
A vulnerability allowing authorization bypass has been identified in the AIKTP plugin for WordPress, affecting all versions through 5.0.7. The issue arises because the plugin's synchronization token, 'aiktpz_token', is created using PHP's 'uniqid()' function, which generates a non-cryptographic, time-based value with roughly one million microsecond candidates per uncertain generation second. This predictable token can be exploited through the unauthenticated, unthrottled REST endpoint '/wp-json/aiktp/checkToken', which serves as a public brute-force oracle for the token. The vulnerability is compounded by the fact that the capability checks in 'check_valid_token' and its associated functions only reference a server-stored Administrator account rather than the actual REST caller. As a result, possession of the token alone grants Administrator-level access to any external request. Exploiting this vulnerability allows unauthenticated attackers to retrieve the sync token and use it to publish posts as a site Administrator, overwrite existing post content, or upload media and designate it as the featured image for any post. Furthermore, if the 'aiktpz_token' option has never been set, the 'checkToken' oracle will erroneously validate an empty token submission, creating a no-effort bypass that requires no brute-forcing.
No known patch is available. It is recommended to review the vulnerability details thoroughly and consider uninstalling the affected plugin.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Nov 19, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-285 | Improper Authorization | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| AIKTP | <= 5.0.7 (semver) |
CPE
Remediation
| |
Change History
1 change record found show changes
| Date | Action | Recorded By |
|---|---|---|
| Nov 19, 2026 | New CVE Received | [email protected] |
Volerion