{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-11682 exists.","fix":"No fix has been published for CVE-2025-11682 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-11682 is a high-severity cross-site scripting vulnerability in Perx Technologies Customer Engagement \u0026 Loyalty Platform, published on 27 Oct 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-11682 and fix it if it is affected.\n\nWhat it is: CVE-2025-11682 is a high-severity cross-site scripting vulnerability in Perx Technologies Customer Engagement \u0026 Loyalty Platform, published on 27 Oct 2025. It can only be exploited from the same machine or local 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-11682 exists.\n\nAffected product: Perx Technologies Customer Engagement \u0026 Loyalty Platform. 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-2025-11682/ (Markdown: https://insights.sbomify.com/CVE-2025-11682/index.md)","id":"CVE-2025-11682","markdown":"https://insights.sbomify.com/CVE-2025-11682/index.md","name":"CVE-2025-11682","record":{"aliases":["GHSA-qxmp-vwjw-x542"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Customer Engagement Platform","requires_auth":"high_privilege","summary":"An authenticated attacker can inject malicious JavaScript via SVG uploads, leading to session hijacking and data theft for other users.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"NCSC.ch","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:A/AC:H/AT:N/PR:H/UI:A/VC:H/VI:H/VA:N/SC:H/SI:H/SA:L","version":"4.0"},"cwes":[{"id":"CWE-83","name":"Improper Neutralization of Script in Attributes in a Web Page"},{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Stored cross-site scripting (XSS) vulnerability in the LMT Dashboard of the Perx Customer Engagement \u0026 Loyalty Platform allows an authenticated attacker to execute arbitrary JavaScript code in a victim's browser. The vulnerability is due to improper sanitization of SVG file uploads. An attacker can upload a malicious SVG file containing a script payload to a campaign. When another user views this image on the public LMT microsite, the script executes, which can lead to session hijacking, data theft, or other unauthorized actions.This issue affects Customer Engagement \u0026 Loyalty Platform before 4.617.4.","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":"Stored Cross-Site Scripting in Perx Customer Engagement \u0026 Loyalty Platform","id":"CVE-2025-11682","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in YAML::Syck","id":"CVE-2025-11683"},"packages":[],"prev":{"headline":"Denial of Service condition in M-Files Server","id":"CVE-2025-11681"},"products":["Customer Engagement \u0026 Loyalty Platform"],"published":"2025-10-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-27","vendors":["Perx Technologies"]},"summary":"An authenticated attacker can inject malicious JavaScript via SVG uploads, leading to session hijacking and data theft for other users.","url":"https://insights.sbomify.com/CVE-2025-11682/"}