Translation with DeepL API vulnerabilities
Plugin slug wpdeepl · 3 known vulnerabilities · latest disclosed 2023-10-25 · WordPress.org page
Every listed vulnerability has a fix. Version 2.4.1.2 or later is not affected by any of them. If your site runs an older version, update it.
0 of 3 rated high or critical (CVSS 7 or more).
Known vulnerabilities in Translation with DeepL API
| Severity | Affected versions | Fixed in | CVE | Published | Details |
|---|---|---|---|---|---|
| Medium 4.3 | <= 2.4.1.1 | 2.4.1.2 | CVE-2023-46620 | 2023-10-25 | Advisory |
| Medium 4.3 | <= 2.1.4 | 2.1.5 | CVE-2023-27446 | 2023-03-02 | Advisory |
| Medium 6.5 | <= 1.7.4 | 1.7.5 | CVE-2022-3691 | 2022-10-31 | Advisory |
Check if a site is affected
Enter a site address to see which version of Translation with DeepL API and other plugins it runs, and whether they match a known vulnerability.
Questions
Is the Translation with DeepL API plugin safe to use?
All 3 known issues are fixed in current versions (2.4.1.2 or later). Keeping it updated is what matters.
How do I check which version of Translation with DeepL API my site runs?
In WordPress go to Plugins > Installed Plugins. From the outside, the free PluginPeek scan below reads the version from the site's public files.
How do I fix a vulnerable plugin?
Make a full backup, then update it from Dashboard > Updates and check the site afterwards. If you would rather not, we can do it for a fixed $99, paid after you have checked the site.