dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-25026

HIGH · 7.5 CVSS v3.1 Published 2026-03-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Missing Authorization vulnerability in RadiusTheme Team tlp-team allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Team: from n/a through <= 5.0.11.

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 · moderate confidence

Missing authorization vulnerability in the RadiusTheme Team (tlp-team) WordPress plugin allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized access to sensitive team management functionality or data without proper authentication or privilege validation.

MitigationUpdate to the latest patched version of the tlp-team plugin when available, and conduct a security review of all access control configurations to ensure proper authorization checks are enforced on sensitive endpoints.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 tlp-team plugin installation
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or check the /wp-content/plugins/tlp-team/ directory via file manager or SSH
    Affected if The tlp-team plugin by RadiusTheme is present and active on the WordPress site
  2. Identify installed plugin version
    In WordPress admin, find the tlp-team plugin entry and note the version number displayed, or read the main plugin file header in /wp-content/plugins/tlp-team/tlp-team.php
    Affected if The installed version is older than the patched version released to address CVE-2026-25026
  3. Inspect plugin access control configuration
    Review the plugin settings in WordPress admin under TLP Team > Team Settings, checking any security level, access permission, or visibility settings that control who can access team management features
    Affected if Access control settings are configured with weak or overly permissive security levels that allow unauthenticated or low-privilege access
  4. Test for unauthorized endpoint access
    Using a web request tool (curl or browser developer tools), send requests to common tlp-team AJAX endpoints (typically /wp-admin/admin-ajax.php?action=tlp_team_*) without valid authentication or with a low-privilege user account
    Affected if Requests succeed and return sensitive team data or management functionality without proper authorization validation
  5. Review capability checks in plugin code
    Examine the main plugin PHP files for capability checks (current_user_can, wp_verify_nonce, etc.) around team management functions, particularly in files handling member listing, addition, or modification
    Affected if No or inadequate capability checks exist before executing sensitive team operations, indicating the missing authorization vulnerability is present

A user is affected if the tlp-team plugin is installed, the installed version predates the patched release for CVE-2026-25026, and the plugin exposes team management functionality without proper authorization verification.

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 to the latest patched version of the tlp-team plugin when available, and conduct a security review of all access control configurations to ensure proper authorization checks are enforced on sensitive endpoints.

Recommended fix Moderate confidence

Latest available version of the Team plugin (check WordPress plugin repository for current release)

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Team' plugin by RadiusTheme (tlp-team)
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin is functioning correctly on your site
  6. 6. Test the access control functionality to confirm the authorization vulnerability is resolved
Caveat Review plugin settings after update as default configurations may have changed

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25026 — 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-25026 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