dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2025-25303

MEDIUM · 6.9 CVSS v4.0 Published 2025-03-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The MouseTooltipTranslator Chrome extension allows mouseover translation of any language at once. The MouseTooltipTranslator browser extension is vulnerable to SSRF attacks. The pdf.mjs script uses the URL parameter from the current URL as the file to download and display to the extension user. Because pdf.mjs is imported in viewer.html and viewer.html is accessible to all URLs, an attacker can force the user’s browser to make a request to any arbitrary URL. After discussion with maintainer, patching this issue would require disabling a major feature of the extension in exchange for a low severity vulnerability. Decision to not patch issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The MouseTooltipTranslator Chrome extension contains a Server-Side Request Forgery (SSRF) vulnerability in the pdf.mjs script. The script uses a URL parameter from the current page URL to determine which file to download and display. Since pdf.mjs is imported in viewer.html, which is accessible to all URLs, an attacker can craft a malicious link that forces the user's browser to make requests to arbitrary URLs, potentially exposing internal services or triggering unintended actions.

MitigationIf the extension must be used, avoid clicking untrusted links that may contain malicious viewer.html URL parameters. Consider using alternative translation extensions that receive security updates, as the maintainer has elected not to patch this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if MouseTooltipTranslator extension is installed
    Open Chrome and navigate to chrome://extensions, then look for 'MouseTooltipTranslator' in the list of installed extensions
    Affected if The extension is listed as installed
  2. Locate the extension ID
    On the extensions page, find the ID for MouseTooltipTranslator (a 32-character string) and navigate to the extension's installation folder (typically C:\Users\<username>\AppData\Local\Google\Chrome\User Data\Default\Extensions\<extension_id> on Windows, or ~/.config/google-chrome/Default/Extensions/<extension_id> on Linux)
    Affected if The extension folder exists and contains files
  3. Verify presence of vulnerable pdf.mjs script
    Within the extension folder, locate the pdf.mjs file and confirm it uses a URL parameter from the page URL to determine which file to download (search for code that reads URL parameters for file paths)
    Affected if The pdf.mjs file exists and contains code that processes URL parameters for file fetching
  4. Confirm viewer.html imports the vulnerable script
    Find viewer.html in the extension folder and verify it imports or includes pdf.mjs
    Affected if viewer.html exists and loads pdf.mjs, making the SSRF reachable via crafted URLs
  5. Test SSRF reachability
    If viewer.html is accessible, attempt to access a test URL like viewer.html?url=http://localhost:8080 (or similar internal endpoint) from the browser's address bar to see if the extension makes a request
    Affected if The extension makes outbound requests based on URL parameters without proper validation, indicating the SSRF vulnerability is present

A user is affected if the MouseTooltipTranslator extension is installed and contains the vulnerable pdf.mjs script that processes URL parameters for file downloads without validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

If the extension must be used, avoid clicking untrusted links that may contain malicious viewer.html URL parameters. Consider using alternative translation extensions that receive security updates, as the maintainer has elected not to patch this vulnerability.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-25303 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-25303 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data