GHSA-XGX4-2WGV-4JHM

PDFME has XSS via Unsanitized i18n Label Injection into innerHTML in multiVariableText propPanel

• Session hijacking: Attacker-injected JavaScript can steal authentication cookies and tokens from any user who opens the Designer.
• DOM manipulation: The injected script runs in the application's origin, allowing phishing overlays, form hijacking, or data exfiltration.
• Stored XSS potential: In multi-tenant applications where labels are stored in a database or fetched from an API, a single poisoned label entry affects all users who subsequently open the Designer.
• Scope change: The XSS payload executes in the embedding application's browser context, escaping the pdfme component's security boundary.

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-XGX4-2WGV-4JHM has a CVSS score of 4.4 (Medium). The vector is network-reachable, low 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 (5.5.10); upgrading removes the vulnerable code path.

Kodem intelligence

Replace innerHTML with safe DOM APIs in packages/schemas/src/multiVariableText/propPanel.ts:

// BEFORE (vulnerable):
para.innerHTML =
  typingInstructions +
  ` <code style="color:${safeColorValue}; font-weight:bold;">{` +
  sampleField +
  '}</code>';

// AFTER (safe):
para.appendChild(document.createTextNode(typingInstructions + ' '));
const codeEl = document.createElement('code');
codeEl.style.color = safeColorValue;
codeEl.style.fontWeight = 'bold';
codeEl.textContent = `{${sampleField}}`;
para.appendChild(codeEl);

This ensures that i18n label values are always treated as text content, never parsed as HTML, regardless of their source.

1. What is GHSA-XGX4-2WGV-4JHM? GHSA-XGX4-2WGV-4JHM is a medium-severity cross-site scripting (XSS) vulnerability in @pdfme/schemas (npm), affecting versions <= 5.5.9. It is fixed in 5.5.10. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is GHSA-XGX4-2WGV-4JHM? GHSA-XGX4-2WGV-4JHM has a CVSS score of 4.4 (Medium). 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.
3. Which versions of @pdfme/schemas are affected by GHSA-XGX4-2WGV-4JHM? @pdfme/schemas (npm) versions <= 5.5.9 is affected.
4. Is there a fix for GHSA-XGX4-2WGV-4JHM? Yes. GHSA-XGX4-2WGV-4JHM is fixed in 5.5.10. Upgrade to this version or later.
5. Is GHSA-XGX4-2WGV-4JHM exploitable, and should I be worried? Whether GHSA-XGX4-2WGV-4JHM 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
6. What actually determines whether GHSA-XGX4-2WGV-4JHM 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.
7. How do I fix GHSA-XGX4-2WGV-4JHM? Upgrade @pdfme/schemas to 5.5.10 or later.