{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-2582 exists.","fix":"No fix has been published for CVE-2023-2582 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-2582 is a medium-severity cross-site scripting vulnerability in Strikingly, published on 8 May 2023. 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-2023-2582 and fix it if it is affected.\n\nWhat it is: CVE-2023-2582 is a medium-severity cross-site scripting vulnerability in Strikingly, published on 8 May 2023. An attacker can exploit it over the internet without logging in, 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-2023-2582 exists.\n\nAffected product: Strikingly. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2023-2582/ (Markdown: https://insights.sbomify.com/CVE-2023-2582/index.md)","id":"CVE-2023-2582","markdown":"https://insights.sbomify.com/CVE-2023-2582/index.md","name":"CVE-2023-2582","record":{"aliases":["GHSA-w545-g5fp-84fq"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Strikingly CMS","requires_auth":"none","summary":"Prototype pollution in Strikingly CMS allows reflected XSS via crafted links, enabling arbitrary JavaScript execution in the victim's browser.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"tenable","cpe":[{"product":"strikingly","vendor":"strikingly"}],"cvss":{"score":6.1,"severity":"medium","source":"cisa-adp","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-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"}],"description":"A prototype pollution vulnerability exists in Strikingly CMS which can result in reflected cross-site scripting (XSS) in affected applications and sites built with Strikingly. The vulnerability exists because of Strikingly JavaScript library parsing the URL fragment allows access to the __proto__ or constructor properties and the Object prototype. By leveraging an embedded gadget like jQuery, an attacker who convinces a victim to visit a specially crafted link could achieve arbitrary javascript execution in the context of the user's browser.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Cross-site scripting in Strikingly","id":"CVE-2023-2582","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Code Injection in jsreport/jsreport","id":"CVE-2023-2583"},"packages":[],"prev":{"headline":"AI-Engine \u003c 1.6.83 - Admin+ Stored XSS","id":"CVE-2023-2580"},"products":["Strikingly"],"published":"2023-05-08","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-01-28","vendors":["n/a"]},"summary":"Prototype pollution in Strikingly CMS allows reflected XSS via crafted links, enabling arbitrary JavaScript execution in the victim's browser.","url":"https://insights.sbomify.com/CVE-2023-2582/"}