CVE-2025-50736
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 · uneditedAn open redirect vulnerability exists in Byaidu PDFMathTranslate v1.9.9 that allows attackers to craft URLs that cause the application to redirect users to arbitrary external websites via the file parameter to the /gradio_api endpoint. This vulnerability could be exploited for phishing attacks or to bypass security filters.
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 · moderate confidenceAn open redirect vulnerability exists in Byaidu PDFMathTranslate v1.9.9 where the file parameter in the /gradio_api endpoint accepts arbitrary URLs, allowing attackers to craft malicious links that redirect users to external phishing sites. This occurs due to insufficient validation of the redirect target in the file parameter.
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
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed version of PDFMathTranslateCheck the version file, package.json, or run the application with --version flag. Common locations: pip show pdfmathtranslate, or check the GitHub release tag in the deployed code.Affected if The installed version is v1.9.9 exactly, or if the version cannot be determined but the application was deployed around the time this CVE was published.
-
Confirm the /gradio_api endpoint exists and is accessibleLocate the application source code and search for routes or endpoints registered with /gradio_api or gradio_api. Check the main application file (typically app.py, main.py, or similar) for route definitions.Affected if The endpoint /gradio_api is defined in the application routing.
-
Inspect how the file parameter is handled in the endpointReview the code handling requests to /gradio_api, specifically the function that processes the file parameter. Look for URL validation logic, redirect operations, or location header assignments using the file parameter value.Affected if The file parameter value is used directly in a redirect or Location header without validation against an allowed list of domains or path patterns.
-
Check for input validation on the file parameterSearch the codebase for validation functions that check whether the file parameter contains an external URL versus an internal file path. Look for whitelist logic, domain restriction, or path sanitization.Affected if There is no validation, or the validation allows arbitrary URLs (http:// or https://) to pass through unchecked.
A user is affected if they are running version v1.9.9 of PDFMathTranslate and the /gradio_api endpoint processes the file parameter without validating that it points to an internal resource rather than an external URL.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement strict input validation on the file parameter to ensure only legitimate, internal file paths or whitelisted domains are allowed. Additionally, implement a warning banner or confirmation page before redirects occur.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-50736 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-50736 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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