CVE-2026-110728 json
AIKTP <= 5.0.7 - Unauthenticated Authorization Bypass via Predictable Token via Predictable 'aiktpz_token' + '/checkToken' Brute-Force Oracle
published 22h ago modified 16h ago also EUVD-2026-129504
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 40%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2026-110728 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 16h ago
Exploit prediction
0.45% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-19).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
Affected products
- aiktp AIKTP
Classification
- Weakness
-
- CWE-285 Improper Authorization
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/916ff9fa-04d1-4d15-92dd-905dd6fe259e?source=cve
- plugins.trac.wordpress.org /browser/aiktp/trunk/aiktp.php#L107
- plugins.trac.wordpress.org /browser/aiktp/trunk/includes/aiktp-sync.php#L362
- plugins.trac.wordpress.org /browser/aiktp/trunk/includes/aiktp-sync.php#L401
- plugins.trac.wordpress.org /browser/aiktp/trunk/aiktp.php#L979
- plugins.trac.wordpress.org /browser/aiktp/trunk/includes/aiktp-sync.php#L231
- plugins.trac.wordpress.org /browser/aiktp/trunk/includes/aiktp-sync.php#L602
- plugins.trac.wordpress.org /browser/aiktp/trunk/includes/aiktp-sync.php#L842
Sources
- CVE List CVE-2026-110728
- NVD CVE-2026-110728
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.