CVE-2026-110728
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network without logging in. Limited direct impact.
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- ReservedThe CVE id was reserved by its CNA
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: not scored yet.
- Severity: 5.3 MEDIUM (CVSS).
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Weakness
- CWE-285
- Record status
- Received
Affected
- Aiktp ≤ 5.0.7
Attack profile CVSS 3.1 · 5.3
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-110728.md and follow it. Check whether this project is affected by CVE-2026-110728. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
References
- https://plugins.trac.wordpress.org/browser/aiktp/trunk/aiktp.php#L107
- https://plugins.trac.wordpress.org/browser/aiktp/trunk/aiktp.php#L979
- https://plugins.trac.wordpress.org/browser/aiktp/trunk/includes/aiktp-sync.php#L231
- https://plugins.trac.wordpress.org/browser/aiktp/trunk/includes/aiktp-sync.php#L362
- https://plugins.trac.wordpress.org/browser/aiktp/trunk/includes/aiktp-sync.php#L401
- https://plugins.trac.wordpress.org/browser/aiktp/trunk/includes/aiktp-sync.php#L602
- https://plugins.trac.wordpress.org/browser/aiktp/trunk/includes/aiktp-sync.php#L842
- https://www.wordfence.com/threat-intel/vulnerabilities/id/916ff9fa-04d1-4d15-92dd-905dd6fe259e?source=cve