AIKTP <= 5.0.04 - Missing Authorization to Authenticated (Subscriber+) Multiple Administrator Actions
Strategic Overview
- Status
- Patched in 5.0.05
- Affected Plugin
- AIKTP
- Affected Version
<= 5.0.04- CVSS
- 5.4Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-1103
At a glance
CVE-2026-1103 is a medium-severity Missing Authorization vulnerability in the AIKTP WordPress plugin, affecting versions <= 5.0.04. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 5.0.05; sites on affected versions should update now. Disclosed January 2026, reported by Osvaldo Noe Gonzalez Del Rio (Os).
Vulnerability Overview
The AIKTP plugin for WordPress is vulnerable to unauthorized modification of data due to missing authorization checks on the /aiktp/getToken REST API endpoint in all versions up to, and including, 5.0.04. The endpoint uses the 'verify_user_logged_in' as a permission callback, which only checks if a user is logged in, but fails to verify if the user has administrative capabilities. This makes it possible for authenticated attackers with Subscriber-level access and above to retrieve the administrator's 'aiktpz_token' access token, which can then be used to create posts, upload media library files, and access private content as the administrator.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-862: Missing Authorization
AIKTP <= 5.0.04 carries this weakness at verify_user_logged_in, and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For AIKTP the fix is 5.0.05: builds <= 5.0.04 are affected, anything from 5.0.05 onward is not.
Remediation
Update to version 5.0.05, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: AIKTP 5.0.05 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C