{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-32703 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-32703 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-32703 is a critical cross-site scripting vulnerability in opf openproject, published on 18 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-32703 and fix it if it is affected.\n\nWhat it is: CVE-2026-32703 is a critical cross-site scripting vulnerability in opf openproject, published on 18 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-32703 in the wild and no public exploit code.\n\nAffected product: opf openproject. 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-32703/ (Markdown: https://insights.sbomify.com/CVE-2026-32703/index.md)","id":"CVE-2026-32703","markdown":"https://insights.sbomify.com/CVE-2026-32703/index.md","name":"CVE-2026-32703","record":{"aliases":["GHSA-p423-72h4-fjvp"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Project management software","requires_auth":"low_privilege","summary":"Attackers with repository push access can inject HTML into filenames, causing persistent XSS against project members viewing changesets.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"openproject","vendor":"openproject"}],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"OpenProject is an open-source, web-based project management software. In versions prior to 16.6.9, 17.0.6, 17.1.3, and 17.2.1, the Repositories module did not properly escape filenames displayed from repositories. This allowed an attacker with push access into the repository to create commits with filenames that included HTML code that was injected in the page without proper sanitation. This allowed a persisted XSS attack against all members of this project that accessed the repositories page to display a changeset where the maliciously crafted file was deleted. Versions 16.6.9, 17.0.6, 17.1.3, and 17.2.1 fix the issue.","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":"OpenProject's repository files are served with the MIME type allowing them to be used to bypass Content Security Policy","id":"CVE-2026-32703","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"SiYuan renderSprig: missing admin check allows any user to read full workspace DB","id":"CVE-2026-32704"},"packages":[],"prev":{"headline":"Cleanuparr has Username Enumeration via Timing Attack","id":"CVE-2026-32702"},"products":["openproject"],"published":"2026-03-18","related":[{"cvss_score":9.9,"headline":"OpenProject: SQL Injection in Cost Reporting =n Operator via parse_number_string","id":"CVE-2026-34717","kev_date_added":null,"published":"2026-04-02"},{"cvss_score":9.4,"headline":"Command Injection on OpenProject repositories leads to Remote Code Execution","id":"CVE-2026-25763","kev_date_added":null,"published":"2026-02-06"},{"cvss_score":9.4,"headline":"OpenProject has Argument Injection on Repository module that allows Arbitrary File Write","id":"CVE-2026-24685","kev_date_added":null,"published":"2026-01-28"},{"cvss_score":9.1,"headline":"OpenProject has a SQL Injection via Custom Field Name that can be chained to Remote Code Execution","id":"CVE-2026-32698","kev_date_added":null,"published":"2026-03-18"},{"cvss_score":9.1,"headline":"OpenProject is Vulnerable to Arbitrary File Read via ImageMagick SVG Coder","id":"CVE-2026-22600","kev_date_added":null,"published":"2026-01-10"},{"cvss_score":8.9,"headline":"OpenProject has SSRF and CSWSH in Hocuspocus Synchronization Server","id":"CVE-2026-24772","kev_date_added":null,"published":"2026-01-28"}],"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":"total"},"state":"PUBLISHED","updated":"2026-03-19","vendors":["opf"]},"summary":"Attackers with repository push access can inject HTML into filenames, causing persistent XSS against project members viewing changesets.","url":"https://insights.sbomify.com/CVE-2026-32703/"}