{"answers":{"affected":"2 open source packages ship an affected version, including oro/commerce.","exploited":"There is no known exploitation of GHSA-6f85-3f8q-qc94 in the wild and no public exploit code.","fix":"Upgrade oro/commerce to 5.0.4 or later.","what":"GHSA-6f85-3f8q-qc94 is a cross-site scripting vulnerability in oro/commerce, published on 15 Jul 2022. 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 GHSA-6f85-3f8q-qc94 and fix it if it is affected.\n\nWhat it is: GHSA-6f85-3f8q-qc94 is a cross-site scripting vulnerability in oro/commerce, published on 15 Jul 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of GHSA-6f85-3f8q-qc94 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- oro/commerce (Packagist): affected from 5.0; fixed in 5.0.4\n- oro/commerce (Packagist): affected from 5.0; fixed in 5.0.4\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/GHSA-6f85-3f8q-qc94/ (Markdown: https://insights.sbomify.com/GHSA-6f85-3f8q-qc94/index.md)","id":"GHSA-6f85-3f8q-qc94","markdown":"https://insights.sbomify.com/GHSA-6f85-3f8q-qc94/index.md","name":"GHSA-6f85-3f8q-qc94","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"OroCommerce e-commerce platform","requires_auth":"low_privilege","summary":"Attackers can inject JavaScript via class names in the GrapeJS editor, potentially leading to code execution or account takeover.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"# Impact\nDue to insufficient class name validation in GrapeJS library it's possible to add executable JS code in class name through Selector Manager\n\n# Relates to\n - [https://github.com/artf/grapesjs/issues/4411](https://github.com/artf/grapesjs/issues/4411)\n\n# Patch\nUpdate GrapeJS dependency to \u003e=[v0.19.5](https://github.com/artf/grapesjs/releases/tag/v0.19.5)","ecosystems":["Packagist"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"OroCommerce vulnerable to XSS when adding class name to Selector Manager on pages that use GrapeJS editor","id":"GHSA-6f85-3f8q-qc94","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"xss","year":"2022"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["5.0.4"],"introduced":["5.0"],"last_affected":[],"package":"oro/commerce","purl":null,"source":"GHSA-6f85-3f8q-qc94"},{"ecosystem":"Packagist","fixed":["5.0.4"],"introduced":["5.0"],"last_affected":[],"package":"oro/commerce","purl":"pkg:composer/oro/commerce","source":"GHSA-6f85-3f8q-qc94"}],"products":null,"published":"2022-07-15","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can inject JavaScript via class names in the GrapeJS editor, potentially leading to code execution or account takeover.","url":"https://insights.sbomify.com/GHSA-6f85-3f8q-qc94/"}