CVE-2026-1103
Authorization Bypass in AIKTP WordPress Plugin Allows Token Theft
Publication date: 2026-01-24
Last updated on: 2026-01-24
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| unknown_vendor | aiktp | to 5.0.04 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability in the AIKTP WordPress plugin involves an authorization flaw in the /aiktp/getToken REST API endpoint. This endpoint originally only checked if a user was logged in, without verifying if the user had administrative privileges. As a result, any authenticated user with Subscriber-level access or higher could retrieve the administrator's shared secret token ('aiktpz_token'). This token allows attackers to perform administrative actions such as creating posts, uploading media files, and accessing private content as the administrator. The issue was fixed by changing the permission check to require administrative capabilities, ensuring only administrators can retrieve the token. [1, 3]
How can this vulnerability impact me? :
If exploited, this vulnerability allows an attacker with low-level authenticated access (e.g., Subscriber) to obtain the administrator's access token. With this token, the attacker can impersonate the administrator to create posts, upload files to the media library, and access private content. This can lead to unauthorized content creation, data exposure, and potential site compromise, undermining the integrity and confidentiality of your WordPress site. [1, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
You can detect this vulnerability by checking if your WordPress site is running the AIKTP plugin version 5.0.04 or earlier, which contains the flawed /aiktp/getToken REST API endpoint that allows any logged-in user to retrieve the administrator's aiktpz_token. To detect exploitation attempts, monitor REST API requests to the /aiktp/getToken endpoint from users with Subscriber-level access or above. For example, you can use web server logs or tools like curl to test the endpoint. A sample curl command to test token retrieval (if you have credentials for a low-privilege user) is: curl -X GET -b cookies.txt https://yourwordpresssite.com/wp-json/aiktp/getToken where cookies.txt contains authentication cookies for a Subscriber user. If the token is returned, the site is vulnerable. Additionally, you can audit installed plugin versions via WP-CLI: wp plugin list --format=json and check the AIKTP plugin version. If it is 5.0.04 or below, it is vulnerable. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the AIKTP WordPress plugin to version 5.0.05 or later, where the authorization flaw in the /getToken REST API endpoint has been fixed. This update changes the permission callback to require administrative capabilities (manage_options) instead of just being logged in, preventing low-privilege users from retrieving the administrator token. If updating immediately is not possible, restrict access to the /aiktp/getToken REST API endpoint by limiting REST API access to trusted users or IP addresses, or temporarily disable the AIKTP plugin until the update can be applied. [1]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows authenticated users with low privileges to access administrator tokens, enabling unauthorized creation and modification of content and access to private data. This unauthorized access could lead to exposure or alteration of sensitive information, potentially violating data protection requirements under standards like GDPR or HIPAA. By allowing unauthorized data modification and access, the vulnerability undermines the integrity and confidentiality controls required for compliance with such regulations. The fix implemented restricts token access to administrators only, thereby improving compliance posture by enforcing stricter access controls. [1, 3]