{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-23499 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-23499 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-23499 is a high-severity cross-site scripting vulnerability in saleor, published on 21 Jan 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-23499 and fix it if it is affected.\n\nWhat it is: CVE-2026-23499 is a high-severity cross-site scripting vulnerability in saleor, published on 21 Jan 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-23499 in the wild and no public exploit code.\n\nAffected product: saleor. 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-23499/ (Markdown: https://insights.sbomify.com/CVE-2026-23499/index.md)","id":"CVE-2026-23499","markdown":"https://insights.sbomify.com/CVE-2026-23499/index.md","name":"CVE-2026-23499","record":{"aliases":["GHSA-666h-2p49-pg95"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Saleor e-commerce platform","requires_auth":"low_privilege","summary":"Authenticated users can upload malicious files leading to stored XSS and token theft if media is served from the same domain without proper headers.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"saleor","vendor":"saleor"}],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"},{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"Saleor is an e-commerce platform. Starting in version 3.0.0 and prior to versions 3.20.108, 3.21.43, and 3.22.27, Saleor allowed authenticated staff users or Apps to upload arbitrary files, including malicious HTML and SVG files containing Javascript. Depending on the deployment strategy, these files may be served from the same domain as the dashboard without any restrictions leading to the execution of malicious scripts in the context of the user's browser. Malicious staff members could craft script injections to target other staff members, possibly stealing their access and/or refresh tokens. Users are vulnerable if they host the media files inside the same domain as the dashboard, e.g., dashboard is at `example.com/dashboard/` and media are under `example.com/media/`. They are not impact if media files are hosted in a different domain, e.g., `media.example.com`. Users are impacted if they do not return a `Content-Disposition: attachment` header for the media files. Saleor Cloud users are not impacted. This issue has been patched in versions: 3.22.27, 3.21.43, and 3.20.108. Some workarounds are available for those unable to upgrade. Configure the servers hosting the media files (e.g., CDN or reverse proxy) to return the Content-Disposition: attachment header. This instructs browsers to download the file instead of rendering them in the browser. Prevent the servers from returning HTML and SVG files. Set-up a `Content-Security-Policy` for media files, such as `Content-Security-Policy: default-src 'none'; base-uri 'none'; frame-ancestors 'none'; form-action 'none';`.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-04-11","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-04-11T19:15:07Z","kind":"github_poc","ref":"https://github.com/lukasz-rybak/CVE-2026-23499","stars":0,"title":"CVE-2026-23499 - Saleor vulnerable to stored XSS via Unrestricted File Upload"}],"tier":"poc_unverified"},"has_fix":false,"headline":"Saleor vulnerable to stored XSS via Unrestricted File Upload","id":"CVE-2026-23499","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"Dolibarr: OS Command Injection (RCE) via MAIN_ODT_AS_PDF configuration","id":"CVE-2026-23500"},"packages":[],"prev":{"headline":"Shopware Improper Control of Generation of Code in Twig rendered views","id":"CVE-2026-23498"},"products":["saleor"],"published":"2026-01-21","related":[{"cvss_score":8.7,"headline":"Saleor has an Insecure Direct Object Reference (IDOR) in GraphQL API","id":"CVE-2026-24136","kev_date_added":null,"published":"2026-01-23"},{"cvss_score":7.5,"headline":"Saleor Affected by Denial of Service via Unbounded GraphQL Query Batching","id":"CVE-2026-33756","kev_date_added":null,"published":"2026-04-08"},{"cvss_score":7.5,"headline":"Saleor has a resource exhaustion vulnerability in GraphQL queries","id":"CVE-2026-35401","kev_date_added":null,"published":"2026-04-08"},{"cvss_score":7.2,"headline":"Saleor lacks proper HTML sanitization in rich text fields","id":"CVE-2026-22849","kev_date_added":null,"published":"2026-01-21"},{"cvss_score":6.5,"headline":"Saleor is vulnerable to staff-authenticated error message information disclosure vulnerability via Python exceptions","id":"CVE-2023-26051","kev_date_added":null,"published":"2023-03-02"},{"cvss_score":6.5,"headline":"Missing Authorization in saleor/saleor","id":"CVE-2022-0932","kev_date_added":null,"published":"2022-03-11"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-22","vendors":["saleor"]},"summary":"Authenticated users can upload malicious files leading to stored XSS and token theft if media is served from the same domain without proper headers.","url":"https://insights.sbomify.com/CVE-2026-23499/"}