dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-68021

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
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 ConveyThis ConveyThis conveythis-translate allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects ConveyThis: from n/a through <= 269.9.

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

This is a Missing Authorization vulnerability in the ConveyThis WordPress translation plugin. The plugin fails to properly enforce access control checks, allowing attackers to exploit incorrectly configured security levels to access functionality they should not have permission to use. The issue affects all versions through 269.9 and could allow low-privilege or unauthenticated users to perform actions beyond their authorized scope.

MitigationImplement proper capability checks and role-based access control (RBAC) on all sensitive functions and AJAX endpoints within the plugin. Review and fix all locations where user permissions are not validated before executing privileged operations.

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
None
Integrity
Low
Availability
Low

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

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. Identify if ConveyThis plugin is installed
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'ConveyThis Translate' in the list of active plugins.
    Affected if The ConveyThis Translate plugin appears in the installed plugins list, regardless of whether it is active or inactive.
  2. Determine the installed version of ConveyThis
    In the WordPress admin, go to Plugins > Installed Plugins. Find ConveyThis Translate and locate the version number displayed below the plugin name. Compare this version to 269.9.
    Affected if The installed version is 269.9 or any earlier version (e.g., 269.8, 269.0, 1.x, etc.).
  3. Review AJAX endpoints for missing capability checks
    Access the plugin directory via file manager or FTP. Examine the main plugin PHP file and look for AJAX action handlers registered with add_action. Identify which handlers perform sensitive operations (such as updating settings, modifying content, or accessing user data) and verify whether they include current_user_can() or similar capability verification before executing.
    Affected if Any AJAX handler in the plugin performs privileged operations without first checking if the current user has the appropriate capability or role permission.
  4. Inspect admin pages for unprotected functionality
    In the plugin directory, locate files that render admin settings pages or front-end functionality. Search for functions that modify plugin settings, translation data, or site content. Determine whether these functions verify user permissions before allowing modifications.
    Affected if Sensitive functions that modify settings, translations, or content can be accessed or executed without verifying that the user has administrative privileges.
  5. Test access control with a low-privilege account
    Create or use a WordPress user account with a low-privilege role (such as Subscriber). Attempt to access direct URLs or make AJAX requests to suspected protected endpoints within the ConveyThis plugin. Observe whether the requests succeed or are blocked.
    Affected if A low-privilege or unauthenticated user can successfully access or execute functions that should require administrator-level capabilities.

You are affected if the ConveyThis Translate plugin is installed with version 269.9 or earlier, and any sensitive functionality in the plugin lacks proper capability checks before executing privileged operations.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper capability checks and role-based access control (RBAC) on all sensitive functions and AJAX endpoints within the plugin. Review and fix all locations where user permissions are not validated before executing privileged operations.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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