Google Translate Api Browser
Approved changes feed: RSS · Atom
cpe:2.3:a:cjvnjde:google_translate_api_browser:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Cjvnjde (9cfcddaf-28bf-5901-bcf6-c5cef1d880e2) |
|---|---|
| Product | Google Translate Api Browser (2620dcbc-a8c0-5c35-b4c7-e1978c72ea3e) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/cjvnjde/google-translate-api-browser |
purl2cpe | 2026-06-01 10:17:02.368755 |
pkg:npm/google-translate-api-browser |
purl2cpe | 2026-06-01 10:17:02.368757 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2023-48711 |
vulnerable | 2026-06-08 06:14:27.933843 |
Server-Side Request Forgery (SSRF) Vulnerability in google-translate-api-browser
LOW (3.7)
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.
Published: 2023-11-24T17:06:15.019Z
Updated: 2024-08-02T21:37:54.659Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.