Smartcat Translator for WPML <= 3.1.77 - Missing Authorization to Unauthenticated Plugin Settings Update
Strategic Overview
- Status
- Patched in 3.1.78
- Affected Plugin
- Smartcat Translator for WPML
- Affected Version
<= 3.1.77- CVSS
- 6.5Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-4683
At a glance
CVE-2026-4683 is a medium-severity Missing Authorization vulnerability in the Smartcat Translator for WPML WordPress plugin, affecting versions <= 3.1.77. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.1.78; sites on affected versions should update now. Disclosed May 2026, reported by Alexis Lafontaine.
Vulnerability Overview
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 Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
Smartcat Translator for WPML <= 3.1.77 carries this weakness at routeData, and reaching it takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Smartcat Translator for WPML the fix is 3.1.78: builds <= 3.1.77 are affected, anything from 3.1.78 onward is not.
Remediation
Update to version 3.1.78, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Smartcat Translator for WPML 3.1.78 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Smartcat Translator for WPML
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C