{"answers":{"affected":"2 open source packages ship an affected version, including happy-dom.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62410 exists.","fix":"Upgrade happy-dom to 20.0.2 or later.","what":"CVE-2025-62410 is a critical code injection vulnerability in capricorn86 happy-dom, published on 15 Oct 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-62410 and fix it if it is affected.\n\nWhat it is: CVE-2025-62410 is a critical code injection vulnerability in capricorn86 happy-dom, published on 15 Oct 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62410 exists.\n\nAffected packages and fixed versions:\n- happy-dom (npm): affected from 19.0.0; fixed in 20.0.2\n- happy-dom (npm): affected from 19.0.0; fixed in 20.0.2\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-2025-62410/ (Markdown: https://insights.sbomify.com/CVE-2025-62410/index.md)","id":"CVE-2025-62410","markdown":"https://insights.sbomify.com/CVE-2025-62410/index.md","name":"CVE-2025-62410","record":{"aliases":["GHSA-qpm2-6cq5-7pq5"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript DOM library","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary code and escalate privileges via prototype pollution in happy-dom due to insufficient isolation of untrusted JavaScript.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.4,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"}],"description":"In versions before 20.0.2, it was found that --disallow-code-generation-from-strings is not sufficient for isolating untrusted JavaScript in happy-dom. The untrusted script and the rest of the application still run in the same Isolate/process, so attackers can deploy prototype pollution payloads to hijack important references like \"process\" in the example below, or to hijack control flow via flipping checks of undefined property. This vulnerability is due to an incomplete fix for CVE-2025-61927. The vulnerability is fixed in 20.0.2.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"--disallow-code-generation-from-strings is not sufficient for isolating untrusted JavaScript in happy-dom","id":"CVE-2025-62410","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2025"},"n_packages":2,"n_references":2,"next":{"headline":"Stored XSS in Alert Transport name field in LibreNMS","id":"CVE-2025-62411"},"packages":[{"ecosystem":"npm","fixed":["20.0.2"],"introduced":["19.0.0"],"last_affected":[],"package":"happy-dom","purl":null,"source":"GHSA-qpm2-6cq5-7pq5"},{"ecosystem":"npm","fixed":["20.0.2"],"introduced":["19.0.0"],"last_affected":[],"package":"happy-dom","purl":"pkg:npm/happy-dom","source":"GHSA-qpm2-6cq5-7pq5"}],"prev":{"headline":"Envoy allows large requests and responses to cause TCP connection pool crash","id":"CVE-2025-62409"},"products":["happy-dom"],"published":"2025-10-15","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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-10-15","vendors":["capricorn86"]},"summary":"Attackers can execute arbitrary code and escalate privileges via prototype pollution in happy-dom due to insufficient isolation of untrusted JavaScript.","url":"https://insights.sbomify.com/CVE-2025-62410/"}