dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-4683

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-15
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
The Smartcat Translator for WPML plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'routeData' REST endpoint in all versions up to, and including, 3.1.77. This makes it possible for unauthenticated attackers to overwrite the plugin's Smartcat API credentials (account ID, API secret key, hub key, API host, and hub host), effectively hijacking the translation service or causing a denial of service.

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 Smartcat Translator for WPML plugin has a broken access control vulnerability in its REST API endpoint 'routeData', which lacks proper capability verification. This allows any unauthenticated user to send requests that overwrite the plugin's Smartcat API credentials (account ID, API secret key, hub key, API host, and hub host). Attackers can exploit this to hijack translation services or disrupt functionality by corrupting the API configuration.

MitigationApply the latest plugin update (version 3.1.78 or higher) which should include proper capability checks on the REST endpoint. Until patched, consider restricting access to the wp-json endpoint or monitoring for suspicious API credential modifications.

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. Verify Smartcat Translator for WPML plugin is installed
    Go to WordPress admin > Plugins and check if 'Smartcat Translator for WPML' is active, or check the plugin files in /wp-content/plugins/ directory for the smartcat-translator-wpml folder
    Affected if The plugin is installed and active
  2. Check the installed plugin version
    In WordPress admin > Plugins, find the Smartcat Translator for WPML plugin and note the version number displayed. Compare it to the fixed version 3.1.78
    Affected if The installed version is lower than 3.1.78
  3. Test unauthenticated access to the vulnerable REST endpoint
    Send a GET request to /wp-json/smartcat-translator/v1/routeData without providing any authentication credentials (no cookie, no nonce)
    Affected if The endpoint responds without requiring authentication (returns 200 OK instead of 401/403)
  4. Inspect WordPress REST API capability restrictions for the route
    Examine the plugin source code in /wp-content/plugins/smartcat-translator-wpml/includes/ or similar directory, specifically the register_rest_route() call for 'smartcat-translator/v1/routeData' to check if the 'permission_callback' is properly defined
    Affected if The permission_callback is missing, returns true unconditionally, or uses a weak capability check that allows unauthenticated access

You are affected if the plugin is installed with a version below 3.1.78 AND the REST endpoint accepts unauthenticated requests without proper capability 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

Apply the latest plugin update (version 3.1.78 or higher) which should include proper capability checks on the REST endpoint. Until patched, consider restricting access to the wp-json endpoint or monitoring for suspicious API credential modifications.

Recommended fix High confidence

Upgrade to Smartcat Translator for WPML version 3.1.78 or latest available version

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Smartcat Translator for WPML' in the plugin list
  4. Check if current version is 3.1.77 or lower
  5. If vulnerable, click 'Update now' or download latest version from WordPress plugin repository
  6. Verify update completes successfully
  7. Confirm the new version is higher than 3.1.77

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
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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