dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2023-50375

MEDIUM · 5.3 CVSS v3.1 Published 2024-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/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 edo888 Google Language Translator google-language-translator allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Google Language Translator: from n/a through <= 6.0.19.

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

A missing authorization vulnerability exists in the Google Language Translator WordPress plugin (versions through 6.0.19), allowing attackers to exploit incorrectly configured access control security levels. This indicates that certain functions or administrative features lack proper capability checks, potentially permitting unauthenticated or lower-privileged users to access privileged operations.

MitigationUpgrade to a patched version of the Google Language Translator plugin if available, or implement proper WordPress capability checks (e.g., current_user_can()) on all sensitive functions and admin ajax 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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 Google Language Translator plugin is installed
    Check for the plugin directory at wp-content/plugins/google-language-translator/ or look for it in WordPress admin under Plugins
    Affected if Plugin is present in the WordPress installation
  2. Identify the installed plugin version
    Open the main plugin file (google-language-translator.php) and look for the version header comment, or check the version in readme.txt
    Affected if Version is 6.0.19 or any earlier version through 6.0.x
  3. Inspect admin-ajax.php handlers for missing capability checks
    Search the plugin files for add_action("wp_ajax") calls and verify if each handler includes current_user_can() or similar authorization checks before executing sensitive operations
    Affected if AJAX handlers exist without proper capability verification (current_user_can() missing)
  4. Check for unauthenticated access to admin functions
    Examine the plugin code for functions that perform privileged operations (settings changes, translation configuration, API key management) and verify they validate user capabilities
    Affected if Sensitive functions lack authorization checks and can be triggered by unauthenticated or low-privilege users

A user is affected if the Google Language Translator plugin versions 6.0 through 6.0.19 are installed and the plugin's AJAX handlers or sensitive functions lack proper WordPress capability verification (current_user_can() checks).

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

Upgrade to a patched version of the Google Language Translator plugin if available, or implement proper WordPress capability checks (e.g., current_user_can()) on all sensitive functions and admin ajax endpoints.

Recommended fix Moderate confidence

Latest available version from WordPress plugin repository (version > 6.0.19)

  1. Check the WordPress admin panel for the Google Language Translator plugin version installed
  2. Navigate to Plugins > Installed Plugins > Google Language Translator
  3. If the current version is 6.0.19 or below, check for available updates in the WordPress plugins repository
  4. If an update is available, update to the latest version (check WordPress plugin repository for version higher than 6.0.19)
  5. If no update is available from the WordPress repository, consider temporarily disabling the plugin until a patched version is released
  6. Review plugin settings to ensure proper access control configurations are in place
Caveat Review plugin settings after upgrade as configuration may reset; test translation functionality

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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