Skip to content
Fencer Intel
medium —

GHSA-qm7q-q8h9-jg8q json

SAFE_FOR_TEMPLATES bypass: template expressions reassemble when sanitized output is reparsed (nested <form> and orphaned end tags)

published 3d ago modified 3d ago

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository cure53/DOMPurify. GitHub has not reviewed it into the GitHub Advisory Database and no CVE record has reached us yet, so everything here comes from the maintainers alone. Read the full advisory on GitHub.

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

Security advisory published by the maintainers of cure53/DOMPurify for dompurify: the maintainers' own advisory, not a reviewed GitHub Advisory Database entry. The full advisory is on GitHub.

Patch / fix

  • npm dompurify 3.4.18

Is GHSA-qm7q-q8h9-jg8q in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
npm dompurify
<3.4.18
3.4.18

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation
  • CWE-1336 Improper Neutralization of Special Elements Used in a Template Engine

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of cure53/DOMPurify published their own advisory on GitHub. Its facts and headline are shown here; the description stays on GitHub.