CVE-2023-48711: Server-Side Request Forgery (SSRF) Vulnerability in google-translate-api-browser

Severity: low (CVSS 3.7 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.5% probability of exploitation in the next 30 days
Public exploit or detection template: yes
Published: 2023-11-24 · updated 2026-06-17
Weakness: CWE-918

Description

google-translate-api-browser is an npm package which interfaces with the google translate web api. A Server-Side Request Forgery (SSRF) Vulnerability is present in applications utilizing the `google-translate-api-browser` package and exposing the `translateOptions` to the end user. An attacker can set a malicious `tld`, causing the application to return unsafe URLs pointing towards local resources. The `translateOptions.tld` field is not properly sanitized before being placed in the Google translate URL. This can allow an attacker with control over the `translateOptions` to set the `tld` to a payload such as `@127.0.0.1`. This causes the full URL to become `https://translate.google.@127.0.0.1/...`, where `translate.google.` is the username used to connect to localhost. An attacker can send requests within internal networks and the local host. Should any HTTPS application be present on the internal network with a vulnerability exploitable via a GET call, then it would be possible to exploit this using this vulnerability. This issue has been addressed in release version 4.1.3. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Affected products

cjvnjde google-translate-api-browser: before 4.1.3 — fixed in 4.1.3

How to fix

Upgrade to a fixed version: cjvnjde google-translate-api-browser 4.1.3. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2023-48711 or the next vulnerability affects your stack