dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-1103

MEDIUM · 5.4 CVSS v3.1 Published 2026-01-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The AIKTP WordPress plugin has a broken access control vulnerability in its /aiktp/getToken REST API endpoint. The endpoint uses 'verify_user_logged_in' as its permission callback, which only confirms a user is authenticated but does not verify the user has administrative privileges. This allows any logged-in user (Subscriber-level and above) to retrieve the administrator's 'aiktpz_token' access token and perform administrative actions like creating posts, uploading media, and accessing private content.

MitigationUpdate the REST API endpoint's permission callback to require administrative capabilities (e.g., 'manage_options') instead of merely checking user login status, or disable the endpoint until a proper capability check is implemented.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify AIKTP plugin is installed
    Go to WordPress Admin > Plugins and confirm the AIKTP plugin is installed and active, or check the wp-content/plugins/aiktp directory exists
    Affected if The AIKTP plugin is installed and active on the site
  2. Confirm REST endpoint exists
    Send a GET request to /wp-json/aiktp/getToken or /?rest_route=/aiktp/getToken
    Affected if The endpoint returns a response (even an error) indicating the route exists
  3. Test endpoint access with low-privilege user
    Log in as a Subscriber-level user and send a request to /wp-json/aiktp/getToken. Check if the response includes the 'aiktpz_token' value
    Affected if A logged-in user without administrative privileges can retrieve the aiktpz_token from the endpoint
  4. Inspect the permission callback
    Review the plugin source code in wp-content/plugins/aiktp/includes/ or similar directory for the REST route registration, looking for 'permission_callback' => 'verify_user_logged_in'
    Affected if The endpoint's permission callback only checks user login status and does not verify administrative capabilities (e.g., 'manage_options')

If any authenticated user with Subscriber-level access can retrieve the aiktpz_token from the /aiktp/getToken endpoint without being required to have administrative privileges, the environment is affected by CVE-2026-1103.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the REST API endpoint's permission callback to require administrative capabilities (e.g., 'manage_options') instead of merely checking user login status, or disable the endpoint until a proper capability check is implemented.

Recommended fix Moderate confidence

AIKTP version 5.0.05 or later

  1. 1. Log in to the WordPress admin dashboard with administrator privileges.
  2. 2. Navigate to Plugins > Installed Plugins.
  3. 3. Locate the AIKTP plugin in the list.
  4. 4. If an update is available, click 'Update Now' to update the plugin to the latest version.
  5. 5. Alternatively, download the updated plugin from the WordPress plugin repository and upload it via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the /aiktp/getToken endpoint now properly checks for administrative capabilities before returning the token.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1103 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1103 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data