HomeWordPress vulnerabilitiesTranslate WordPress with Weglot 2.0
Translate WordPress with Weglot 2.0 vulnerabilities
Translate WordPress with Weglot 2.0 has 2 known vulnerabilities in this database. The most recent published record is dated 30 Oct 2025.
- Known vulnerabilities
- 2
- Active installs
- 50,000+
- Latest version
- 6.4.2
- Last updated
- 1 Oct 2026
- Most recent
- 30 Oct 2025
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Broken access control CVE-2025-10008 | Medium 5.3 | Up to 5.1 | Fixed in a later version (latest 6.4.2) | 30 Oct 2025 |
| Cross-site scripting (XSS) CVE-2024-2124 | Medium 6.4 | Up to 4.2.5 | Fixed in a later version (latest 6.4.2) | 20 Mar 2024 |
Read the published descriptions
- CVE-2025-10008, 30 Oct 2025
- The Translate WordPress and go Multilingual - Weglot plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the 'clean_options' function in all versions up to, and including, 5.1. This makes it possible for unauthenticated attackers to delete limited transients that contain cached plugin options. CVE record
- CVE-2024-2124, 20 Mar 2024
- The Translate WordPress and go Multilingual - Weglot plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's widget/block in all versions up to, and including, 4.2.5 due to insufficient input sanitization and output escaping on user supplied attributes such as 'className'. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
What to do if you run Translate WordPress with Weglot 2.0
If you run Translate WordPress with Weglot 2.0, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Translate WordPress with Weglot 2.0 vulnerabilities
Free. We email you when a new vulnerability is published for Translate WordPress with Weglot 2.0, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.