AIKTP authorization bypass via predictable sync token
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
The AIKTP plugin for WordPress has an authorization bypass caused by a predictable sync token. A remote attacker who needs no login can recover that token, then publish posts attributed to a site administrator, overwrite the content of existing posts, and attach imported images as featured images. The flaw is reached over the network without logging in.
Written by a model
Original 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.
What to do
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-110728 (AIKTP <= 5.0.7 - Unauthenticated Authorization Bypass via Predictable Token via Predictable 'aiktpz_token' + '/checkToken' Brute-Force…), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-110728 (entry last updated 2026-11-19):
Affected:
- aiktp AIKTP: through 5.0.7
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-110728 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-110728 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/916ff9fa-04d1-4d15-92dd-905dd6fe259e?source=cve
- https://plugins.trac.wordpress.org/browser/aiktp/trunk/aiktp.php#L107
- 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/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#L602
- https://plugins.trac.wordpress.org/browser/aiktp/trunk/includes/aiktp-sync.php#L842
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-110728
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-110728"}.Affected versions
- aiktp AIKTPthrough 5.0.7
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch5/5No patch listed yet
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 35 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Evidence 10
Questions about CVE-2026-110728
Is CVE-2026-110728 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-110728?
AIKTP: through 5.0.7.
Source: cve.now feed data
Related
- CVE-2026-1103AIKTP <= 5.0.04 - Missing Authorization to Authenticated (Subscriber+) Multiple Administrator Actions
- CVE-2026-86094Dimension Session Hijack via Exposed Session Tokens in Diagnostic Logs
- CVE-2026-84322Dimension Session Hijack via Exposed Session Tokens in Management API
- CVE-2026-93917Dimension Improper Authorization in Device Registration Allows Managed Device Takeover
- CVE-2026-132144MISP: Non-admin users can change login email under external authentication to capture a directory identity
- CVE-2026-128664An insecure password reset vulnerability in the Admin Password Recovery Module of PHPGurukul News Portal Project v4.1 allows…
No corrections so far. Something wrong on this page? Report an error.