# CVE-2026-1103: AIKTP <= 5.0.04 - Missing Authorization to Authenticated (Subscriber+) Multiple Administrator Actions

> Authenticated subscribers can retrieve admin tokens to perform administrative actions like creating posts and uploading files due to missing authorization checks.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jan 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-xfxj-hhhx-9jv8

## What is CVE-2026-1103?

CVE-2026-1103 is a medium-severity missing authorization vulnerability in AIKTP, published on 24 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-1103?


## How do I fix CVE-2026-1103?

No fix has been published for CVE-2026-1103 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-1103 being exploited?

There is no known exploitation of CVE-2026-1103 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-1103 and fix it if it is affected.

What it is: CVE-2026-1103 is a medium-severity missing authorization vulnerability in AIKTP, published on 24 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-1103 in the wild and no public exploit code.

Affected product: AIKTP. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-1103/ (Markdown: https://insights.sbomify.com/CVE-2026-1103/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-1103
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-1103
- OSV: https://osv.dev/vulnerability/CVE-2026-1103

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-1103/
Summaries are generated and may contain mistakes; the official description above is the record.