{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-25156 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-25156 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-25156 is a high-severity cross-site scripting vulnerability in kohler hotcrp, published on 30 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-25156 and fix it if it is affected.\n\nWhat it is: CVE-2026-25156 is a high-severity cross-site scripting vulnerability in kohler hotcrp, published on 30 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-25156 in the wild and no public exploit code.\n\nAffected product: kohler hotcrp. 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-25156/ (Markdown: https://insights.sbomify.com/CVE-2026-25156/index.md)","id":"CVE-2026-25156","markdown":"https://insights.sbomify.com/CVE-2026-25156/index.md","name":"CVE-2026-25156","record":{"aliases":["GHSA-p88p-2f2p-2476"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Conference review software","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary JavaScript in victims' browsers via malicious document uploads, potentially stealing credentials and accessing APIs.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"hotcrp","vendor":"hotcrp"}],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"HotCRP is conference review software. HotCRP versions from October 2025 through January 2026 delivered documents of all types with inline Content-Disposition, causing them to be rendered in the user’s browser rather than downloaded. (The intended behavior was for only `text/plain`, `application/pdf`, `image/gif`, `image/jpeg`, and `image/png` to be delivered inline, though adding `save=0` to the document URL could request inline delivery for any document.) This made users who clicked a document link vulnerable to cross-site scripting attacks. An uploaded HTML or SVG document would run in the viewer’s browser with access to their HotCRP credentials, and Javascript in that document could eventually make arbitrary calls to HotCRP’s API. Malicious documents could be uploaded to submission fields with “file upload” or “attachment” type, or as attachments to comments. PDF upload fields were not vulnerable. A search of documents uploaded to hotcrp.com found no evidence of exploitation. The vulnerability was introduced in commit aa20ef288828b04550950cf67c831af8a525f508 (11 October 2025), present in development versions and v3.2, and fixed in commit 8933e86c9f384b356dc4c6e9e2814dee1074b323 and v3.2.1. Additionally, c3d88a7e18d52119c65df31c2cc994edd2beccc5 and v3.2.1 remove support for `save=0`.","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":"HotCRP vulnerable to stored XSS via comment attachments","id":"CVE-2026-25156","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"OpenClaw/Clawdbot has OS Command Injection via Project Root Path in sshNodeCommand","id":"CVE-2026-25157"},"packages":[],"prev":{"headline":"Qwik City CSRF protection middleware does not work properly for content type header with parameters (eg. multipart/form-data)","id":"CVE-2026-25155"},"products":["hotcrp"],"published":"2026-01-30","related":[{"cvss_score":10,"headline":"HotCRP vulnerable to remote code execution through formulas","id":"CVE-2026-23836","kev_date_added":null,"published":"2026-01-19"},{"cvss_score":6.5,"headline":"HotCRP vulnerable to exposure of submitted documents","id":"CVE-2026-23878","kev_date_added":null,"published":"2026-01-19"},{"cvss_score":2.4,"headline":"HotCRP cross site scripting","id":"CVE-2022-4819","kev_date_added":null,"published":"2022-12-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":"partial"},"state":"PUBLISHED","updated":"2026-02-02","vendors":["kohler"]},"summary":"Attackers can execute arbitrary JavaScript in victims' browsers via malicious document uploads, potentially stealing credentials and accessing APIs.","url":"https://insights.sbomify.com/CVE-2026-25156/"}