{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-32751 exists.","fix":"No fix has been published for CVE-2023-32751 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-32751 is a medium-severity cross-site scripting vulnerability in n/a, published on 8 Jun 2023. 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-2023-32751 and fix it if it is affected.\n\nWhat it is: CVE-2023-32751 is a medium-severity cross-site scripting vulnerability in n/a, published on 8 Jun 2023. Any signed-in user can exploit it over the 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-2023-32751 exists.\n\nAffected product: n/a. 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-32751/ (Markdown: https://insights.sbomify.com/CVE-2023-32751/index.md)","id":"CVE-2023-32751","markdown":"https://insights.sbomify.com/CVE-2023-32751/index.md","name":"CVE-2023-32751","record":{"aliases":["GHSA-r9f7-x9f6-fp64"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Pydio Cells","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary JavaScript via stored XSS in Pydio Cells by exploiting hardcoded signing secrets to serve malicious HTML files inline.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"cells","vendor":"pydio"}],"cvss":{"score":5.4,"severity":"medium","source":"cisa-adp","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":"Pydio Cells through 4.1.2 allows XSS. Pydio Cells implements the download of files using presigned URLs which are generated using the Amazon AWS SDK for JavaScript [1]. The secrets used to sign these URLs are hardcoded and exposed through the JavaScript files of the web application. Therefore, it is possible to generate valid signatures for arbitrary download URLs. By uploading an HTML file and modifying the download URL to serve the file inline instead of as an attachment, any included JavaScript code is executed when the URL is opened in a browser, leading to a cross-site scripting vulnerability.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2023-05-31","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2023-05-31","kind":"exploitdb","ref":"51497","stars":null,"title":"Pydio Cells 4.1.2 - Cross-Site Scripting (XSS) via File Download"}],"tier":"weaponised"},"has_fix":false,"headline":"Cross-site scripting in n/a","id":"CVE-2023-32751","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"L7 Networks InstantScan \u0026 InstantQoS - Arbitrary File Upload","id":"CVE-2023-32752"},"packages":[],"prev":{"headline":"Server-side request forgery in n/a","id":"CVE-2023-32750"},"products":["n/a"],"published":"2023-06-08","related":[{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2023-32749","kev_date_added":null,"published":"2023-06-08"},{"cvss_score":8.8,"headline":"Path traversal in n/a","id":"CVE-2019-12901","kev_date_added":null,"published":"2019-06-19"},{"cvss_score":8.1,"headline":"Path traversal in n/a","id":"CVE-2020-12851","kev_date_added":null,"published":"2020-06-04"},{"cvss_score":7.2,"headline":"Command injection in n/a","id":"CVE-2020-12847","kev_date_added":null,"published":"2020-06-04"},{"cvss_score":7,"headline":"The following vulnerability applies only to the Pydio Cells Enterprise OVF version 2.0.4.","id":"CVE-2020-12850","kev_date_added":null,"published":"2020-06-11"},{"cvss_score":6.8,"headline":"Code injection in n/a","id":"CVE-2020-12852","kev_date_added":null,"published":"2020-06-04"},{"cvss_score":6.5,"headline":"Server-side request forgery in n/a","id":"CVE-2023-32750","kev_date_added":null,"published":"2023-06-08"}],"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":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-01-06","vendors":["n/a"]},"summary":"Attackers can execute arbitrary JavaScript via stored XSS in Pydio Cells by exploiting hardcoded signing secrets to serve malicious HTML files inline.","url":"https://insights.sbomify.com/CVE-2023-32751/"}