# CVE-2026-4683: Smartcat Translator for WPML <= 3.1.77 - Missing Authorization to Unauthenticated Plugin Settings Update

> Unauthenticated attackers can overwrite Smartcat API credentials via a missing capability check, hijacking translation services or causing denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 May 2026
- **Updated:** 15 May 2026
- **Also known as:** GHSA-3rhq-g36f-cvc7

## What is CVE-2026-4683?

CVE-2026-4683 is a medium-severity missing authorization vulnerability in smartcatai Smartcat Translator for WPML, published on 15 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-4683?


## How do I fix CVE-2026-4683?

No fix has been published for CVE-2026-4683 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-4683 being exploited?

There is no known exploitation of CVE-2026-4683 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-4683 and fix it if it is affected.

What it is: CVE-2026-4683 is a medium-severity missing authorization vulnerability in smartcatai Smartcat Translator for WPML, published on 15 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-4683 in the wild and no public exploit code.

Affected product: smartcatai Smartcat Translator for WPML. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-4683/ (Markdown: https://insights.sbomify.com/CVE-2026-4683/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-4683
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-4683
- OSV: https://osv.dev/vulnerability/CVE-2026-4683

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-4683/
Summaries are generated and may contain mistakes; the official description above is the record.