{"answers":{"affected":"2 open source packages ship an affected version, including xhtml-purifier.","exploited":"There is no known exploitation of CVE-2026-61784 in the wild and no public exploit code.","fix":"Upgrade xhtml-purifier to 0.4.3 or later.","what":"CVE-2026-61784 is a medium-severity cross-site scripting vulnerability in cstigler node-xhtml-purifier, published on 24 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-61784 and fix it if it is affected.\n\nWhat it is: CVE-2026-61784 is a medium-severity cross-site scripting vulnerability in cstigler node-xhtml-purifier, published on 24 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-61784 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- xhtml-purifier (npm): affected all versions; fixed in 0.4.3\n- xhtml-purifier (npm): affected all versions; fixed in 0.4.3\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-61784/ (Markdown: https://insights.sbomify.com/CVE-2026-61784/index.md)","id":"CVE-2026-61784","markdown":"https://insights.sbomify.com/CVE-2026-61784/index.md","name":"CVE-2026-61784","record":{"aliases":["GHSA-j8r4-32c5-33rc"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js HTML sanitizer","requires_auth":"none","summary":"Attackers can inject JavaScript via unencoded attribute values in xhtml-purifier, bypassing sanitization to execute scripts in victim browsers.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"},{"id":"CWE-116","name":"Improper Encoding or Escaping of Output"}],"description":"xhtml-purifier is a Node.js library to take in raw/unknown/untrusted HTML and output cleaned, purified, trusted HTML. Versions prior to 0.4.3 do not HTML-entity-encode attribute values when serializing its sanitized output. In attributeString() (XHTMLPurifier.js, around line 148) the attribute value is concatenated directly into a double-quoted attribute without encoding. As a result, an attacker-controlled value in any allowed attribute (class, style, title, alt, src, href) can include a double-quote character to break out of the attribute and inject an additional attribute, such as a JavaScript event handler (for example onmouseover or onerror). The injected handler survives sanitization and executes when the output is rendered, which is a sanitizer bypass leading to cross-site scripting. The fix in version 0.4.3 HTML-entity-encodes attribute values before serialization.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"xhtml-purifier has HTML attribute-injection (sanitizer bypass) that leads to XSS","id":"CVE-2026-61784","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"xss","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"@bytebase/dbhub's read-only mode does not prevent database writes","id":"CVE-2026-61788"},"packages":[{"ecosystem":"npm","fixed":["0.4.3"],"introduced":["0"],"last_affected":[],"package":"xhtml-purifier","purl":null,"source":"GHSA-j8r4-32c5-33rc"},{"ecosystem":"npm","fixed":["0.4.3"],"introduced":["0"],"last_affected":[],"package":"xhtml-purifier","purl":"pkg:npm/xhtml-purifier","source":"GHSA-j8r4-32c5-33rc"}],"prev":{"headline":"Wazuh: RBAC permission-effect check in mask_sensitive_config allows low-privilege users to read cluster.key","id":"CVE-2026-61783"},"products":["node-xhtml-purifier"],"published":"2026-09-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-24","vendors":["cstigler"]},"summary":"Attackers can inject JavaScript via unencoded attribute values in xhtml-purifier, bypassing sanitization to execute scripts in victim browsers.","url":"https://insights.sbomify.com/CVE-2026-61784/"}