What is GHSA-4M3G-6R7G-JV4F?

GHSA-4M3G-6R7G-JV4F is a low-severity cross-site scripting (XSS) vulnerability in gradio_pdf (pip), affecting versions < 0.0.10. It is fixed in 0.0.10. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

How severe is GHSA-4M3G-6R7G-JV4F?

GHSA-4M3G-6R7G-JV4F has a CVSS score of 3.6 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of gradio_pdf are affected by GHSA-4M3G-6R7G-JV4F?

gradio_pdf (pip) versions < 0.0.10 is affected.

Is there a fix for GHSA-4M3G-6R7G-JV4F?

Yes. GHSA-4M3G-6R7G-JV4F is fixed in 0.0.10. Upgrade to this version or later.

Is GHSA-4M3G-6R7G-JV4F exploitable, and should I be worried?

Whether GHSA-4M3G-6R7G-JV4F is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-4M3G-6R7G-JV4F is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-4M3G-6R7G-JV4F in gradio_pdf

Q: How severe is GHSA-4M3G-6R7G-JV4F?

GHSA-4M3G-6R7G-JV4F has a CVSS score of 3.6 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of gradio_pdf are affected by GHSA-4M3G-6R7G-JV4F?

gradio_pdf (pip) versions < 0.0.10 is affected.

Q: Is there a fix for GHSA-4M3G-6R7G-JV4F?

Yes. GHSA-4M3G-6R7G-JV4F is fixed in 0.0.10. Upgrade to this version or later.

Q: Is GHSA-4M3G-6R7G-JV4F exploitable, and should I be worried?

Whether GHSA-4M3G-6R7G-JV4F is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-4M3G-6R7G-JV4F is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-4M3G-6R7G-JV4F?

Upgrade gradio_pdf to 0.0.10 or later.

Summary

Arbitrary JavaScript execution due to using outdated libraries

gradio-pdf projects with dependencies on the pdf.js library are vulnerable to CVE-2024-4367, which allows arbitrary JavaScript execution.

PoC

Generate a pdf file with a malicious script in the fontmatrix. (This will run alert(‘XSS’).)
poc.pdf
Run the app. In this PoC, I've used the demo for a simple proof.
Upload a PDF file containing the script.
Check that the script is running.

Mitigation

Upgrade the pdf.js to v4.2.67, which removes the vulnerability. (or set the option isEvalSupported to false.)

Reference

Impact

Malicious scripts can be injected into the code, and when linked with vulnerabilities such as CSRF, it can cause even greater damage. In particular, It can become a source of further attacks, especially when linked to social engineering.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

GHSA-4M3G-6R7G-JV4F has a CVSS score of 3.6 (Low). The vector is requires local access, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.0.10); upgrading removes the vulnerable code path.

Affected versions

gradio_pdf (< 0.0.10)

Security releases

gradio_pdf → 0.0.10 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade gradio_pdf to 0.0.10 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-4M3G-6R7G-JV4F? GHSA-4M3G-6R7G-JV4F is a low-severity cross-site scripting (XSS) vulnerability in gradio_pdf (pip), affecting versions < 0.0.10. It is fixed in 0.0.10. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
How severe is GHSA-4M3G-6R7G-JV4F? GHSA-4M3G-6R7G-JV4F has a CVSS score of 3.6 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of gradio_pdf are affected by GHSA-4M3G-6R7G-JV4F? gradio_pdf (pip) versions < 0.0.10 is affected.
Is there a fix for GHSA-4M3G-6R7G-JV4F? Yes. GHSA-4M3G-6R7G-JV4F is fixed in 0.0.10. Upgrade to this version or later.
Is GHSA-4M3G-6R7G-JV4F exploitable, and should I be worried? Whether GHSA-4M3G-6R7G-JV4F is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-4M3G-6R7G-JV4F is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-4M3G-6R7G-JV4F? Upgrade gradio_pdf to 0.0.10 or later.