Skip to content
Fencer Intel
medium 5.0

CVE-2021-34630 json

Reflected XSS in GTranslate Pro and GTranslate Enterprise < 2.8.65

published 5y ago modified 4mo ago also EUVD-2021-21280

cvss
5.0
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.6%
EPSS 1.6% chance of exploitation in 30 days, percentile 75%
public exploits
0
none known, plus a Nuclei check

Summary

In the Pro and Enterprise versions of GTranslate < 2.8.65, the gtranslate_request_uri_var function runs at the top of all pages and echoes out the contents of $_SERVER['REQUEST_URI']. Although this uses addslashes, and most modern browsers automatically URLencode requests, this plugin is still vulnerable to Reflected XSS in older browsers such as Internet Explorer 9 or below, or in cases where an attacker is able to modify the request en route between the client and the server, or in cases where the user is using an atypical browsing solution.

Patch / fix

  • gtranslate gtranslate 2.8.65

Is CVE-2021-34630 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.57% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Nuclei template GTranslate < 2.8.65 - Cross-Site Scripting nuclei detection template
  • plugins.svn.wordpress.org https://plugins.svn.wordpress.org/gtranslate/tags/2.8.64/gtranslate.php referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 5.0 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L
NVD 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N

Affected products

  • Translate AI Multilingual Solutions GTranslate Pro and GTranslate Enterprise

Classification

Weakness
  • CWE-116 Improper Encoding or Escaping of Output
  • CWE-79 Improper Neutralization of Input During Web Page Generation
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.