{"answers":{"affected":"2 open source packages ship an affected version, including stage-js. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-53386 exists.","fix":"No fix has been published for CVE-2024-53386 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-53386 is a medium-severity cross-site scripting vulnerability in Piqnt Stage.js, published on 3 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-53386 and fix it if it is affected.\n\nWhat it is: CVE-2024-53386 is a medium-severity cross-site scripting vulnerability in Piqnt Stage.js, published on 3 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-53386 exists.\n\nAffected packages and fixed versions:\n- stage-js (npm): affected all versions up to 0.8.10; no fix listed\n- stage-js (npm): affected all versions up to 0.8.10; no fix listed\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-2024-53386/ (Markdown: https://insights.sbomify.com/CVE-2024-53386/index.md)","id":"CVE-2024-53386","markdown":"https://insights.sbomify.com/CVE-2024-53386/index.md","name":"CVE-2024-53386","record":{"aliases":["GHSA-fp3m-g5rc-4c28"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript library","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary JavaScript via DOM clobbering in Stage.js, potentially compromising user sessions or data.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"stage.js","vendor":"piqnt"}],"cvss":{"score":4.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/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-94","name":"Improper Control of Generation of Code"}],"description":"Stage.js through 0.8.10 allows DOM Clobbering (with resultant XSS for untrusted input that contains HTML but does not directly contain JavaScript), because document.currentScript lookup can be shadowed by attacker-injected HTML elements.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Stage.js DOM Clobbering vulnerabilty","id":"CVE-2024-53386","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"xss","year":"2024"},"n_packages":2,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2024-53387"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.8.10"],"package":"stage-js","purl":null,"source":"GHSA-fp3m-g5rc-4c28"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.8.10"],"package":"stage-js","purl":"pkg:npm/stage-js","source":"GHSA-fp3m-g5rc-4c28"}],"prev":{"headline":"tsup DOM Clobbering vulnerability","id":"CVE-2024-53384"},"products":["Stage.js"],"published":"2025-03-03","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":"US public information, NVD API terms","name":"NVD"},{"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":"partial"},"state":"PUBLISHED","updated":"2025-03-03","vendors":["Piqnt"]},"summary":"Attackers can execute arbitrary JavaScript via DOM clobbering in Stage.js, potentially compromising user sessions or data.","url":"https://insights.sbomify.com/CVE-2024-53386/"}