{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-32095 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-32095 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-32095 is a medium-severity cross-site scripting vulnerability in useplunk plunk, published on 11 Mar 2026. 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-2026-32095 and fix it if it is affected.\n\nWhat it is: CVE-2026-32095 is a medium-severity cross-site scripting vulnerability in useplunk plunk, published on 11 Mar 2026. 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 CVE-2026-32095 in the wild and no public exploit code.\n\nAffected product: useplunk plunk. 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-2026-32095/ (Markdown: https://insights.sbomify.com/CVE-2026-32095/index.md)","id":"CVE-2026-32095","markdown":"https://insights.sbomify.com/CVE-2026-32095/index.md","name":"CVE-2026-32095","record":{"aliases":["GHSA-69jg-7493-cx5x"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Email platform","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary JavaScript in victim browsers by uploading malicious SVG files to the Plunk email platform.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"plunk","vendor":"useplunk"}],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Plunk is an open-source email platform built on top of AWS SES. Prior to 0.7.1, Plunk's image upload endpoint accepted SVG files, which browsers treat as active documents capable of executing embedded JavaScript, creating a stored XSS vulnerability. This vulnerability is fixed in 0.7.1.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Plunk has Stored Cross-Site Scripting (XSS) via SVG File Upload","id":"CVE-2026-32095","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Plunk has SSRF via unvalidated AWS SNS SubscriptionConfirmation in POST /webhooks/sns","id":"CVE-2026-32096"},"packages":[],"prev":{"headline":"Shescape escape() leaves bracket glob expansion active on Bash, BusyBox, and Dash","id":"CVE-2026-32094"},"products":["plunk"],"published":"2026-03-11","related":[{"cvss_score":9.3,"headline":"Plunk has SSRF via unvalidated AWS SNS SubscriptionConfirmation in POST /webhooks/sns","id":"CVE-2026-32096","kev_date_added":null,"published":"2026-03-11"},{"cvss_score":8.5,"headline":"Other in plunk","id":"CVE-2026-34975","kev_date_added":null,"published":"2026-04-06"}],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-12","vendors":["useplunk"]},"summary":"Attackers can execute arbitrary JavaScript in victim browsers by uploading malicious SVG files to the Plunk email platform.","url":"https://insights.sbomify.com/CVE-2026-32095/"}