LiveActive security incident?Get immediate response
CVE Record

CVE-2023-50375: WordPress Translate WordPress – Google Language Translator plugin <= 6.0.19 - Broken Access Control vulnerability

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.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-50375 is a broken access control issue in the WordPress Google Language Translator plugin through version 6.0.19. The CVSS score is 5.3, indicating moderate business risk. The published impact is limited integrity impact, with no confidentiality or availability impact stated in the source bundle.

Executive priority

Treat this as a moderate-priority WordPress hygiene issue. It is unauthenticated and easy to reach, but the documented impact is low integrity only and there is no cited active exploitation. Prioritize internet-facing WordPress sites first.

Technical view

The issue is CWE-862 Missing Authorization in edo888 Google Language Translator, package google-language-translator. The CVSS vector is AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N, meaning network-reachable, low-complexity, unauthenticated exploitation with low integrity impact only.

Likely exposure

Exposure is limited to WordPress installations using the Google Language Translator plugin at version 6.0.19 or earlier. The source bundle does not identify other products, forks, themes, or dependent components as affected.

Exploitation context

The source bundle does not report active exploitation, and the CVE is not listed as KEV. The vulnerability is unauthenticated and network-reachable by CVSS, but no exploit details, proof of concept, or observed campaign evidence is provided.

Researcher notes

Evidence is limited to the CVE metadata and Patchstack reference. The affected range is through 6.0.19. No exploit mechanics, fixed version, patch details, or real-world exploitation evidence are included in the provided bundle.

Mitigation direction

  • Inventory WordPress sites for google-language-translator versions 6.0.19 or earlier.
  • Check Patchstack and vendor guidance for an identified fixed release or mitigation.
  • Do not assume an unpublished fixed version; verify before marking remediated.
  • If the plugin is unnecessary, consider disabling it pending vendor guidance.
  • Monitor WordPress logs for unexpected plugin-related changes or unauthenticated access patterns.

Validation and detection

  • Confirm whether each WordPress site has the Google Language Translator plugin installed.
  • Record the installed plugin version and compare it with the affected range.
  • Review administrative and plugin logs for unexpected setting or content changes.
  • Verify remediation using vendor or Patchstack guidance, not version assumptions.
  • Regression test translation functionality after any update or disablement.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-50375 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2023-50375Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
edo888Google Language Translatorgoogle-language-translator, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.