Security Resilience

CVE-2026-25156

XSS in Hotcrp 3.2

Published
30 January 2026
Modified
19 February 2026
Patch / advisory
CVSS Score v3.1 7.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N
EPSS Score 0.0027 19th percentile
Risk Priority 53 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS scores by FIRST (EPSS SIG), generated by Empirical Security. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-25156 is a high-severity Cross-site Scripting (CWE-79) vulnerability in Hotcrp. Its CVSS base score is 7.3 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Browser Session Hijacking (T1185); ranked at the 19th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-25156 is a cross-site scripting (XSS) vulnerability, classified under CWE-79, in HotCRP, an open-source conference review software. It affects versions from October 2025 through January 2026, including development versions and v3.2. The issue stems from these versions delivering documents of all types with inline Content-Disposition headers, causing browsers to render them inline rather than prompting downloads. Intended inline behavior was limited to text/plain, application/pdf, image/gif, image/jpeg, and image/png types, though the save=0 URL parameter could force inline delivery for others. The vulnerability was introduced in commit aa20ef288828b04550950cf67c831af8a525f508 on 11 October 2025 and carries a CVSS score of 7.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N).

An authenticated attacker with low privileges can exploit this by uploading malicious HTML or SVG documents to submission fields with file upload or attachment types, or as attachments to comments. When a victim clicks the document link, their browser renders the content inline in the HotCRP context, executing JavaScript with access to the victim's HotCRP credentials. This enables the script to make arbitrary calls to HotCRP's API on the victim's behalf. PDF upload fields are not vulnerable, and exploitation requires user interaction to click the link.

Mitigation is available via the fixing commit 8933e86c9f384b356dc4c6e9e2814dee1074b323, included in v3.2.1. An additional commit c3d88a7e18d52119c65df31c2cc994edd2beccc5 in v3.2.1 removes support for the save=0 parameter. Security practitioners should upgrade to v3.2.1 or later and consult the GitHub security advisory at GHSA-p88p-2f2p-2476 for full details.

No evidence of exploitation was found in a search of documents uploaded to hotcrp.com.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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`,…

more

`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`.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1185 Browser Session Hijacking Collection
Adversaries may take advantage of security vulnerabilities and inherent functionality in browser software to change content, modify user-behaviors, and intercept information as part of various browser session hijacking techniques.
T1539 Steal Web Session Cookie Credential Access
An adversary may steal web application or service session cookies and use them to gain access to web applications or Internet services as an authenticated user without needing credentials.
T1189 Drive-by Compromise Initial Access
Adversaries may gain access to a system through a user visiting a website over the normal course of browsing.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1204.001 Malicious Link Execution
An adversary may rely upon a user clicking a malicious link in order to gain execution.
T1491.002 External Defacement Impact
An adversary may deface systems external to an organization in an attempt to deliver messaging, intimidate, or otherwise mislead an organization or users.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-49444Shared CWE-79
CVE-2023-0606Shared CWE-79
CVE-2023-2099Shared CWE-79
CVE-2023-23832Shared CWE-79
CVE-2023-2954Shared CWE-79
CVE-2023-27864Shared CWE-79
CVE-2023-3672Shared CWE-79
CVE-2023-4951Shared CWE-79
CVE-2023-5667Shared CWE-79
CVE-2023-29302Shared CWE-79

Affected Assets

hotcrp
hotcrp
3.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.1.2
  • V1.3.2

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover missing or incorrect input neutralization through targeted web-application tests.

Input validation directly enforces neutralization of untrusted data before it reaches web output generation.

Output filtering can catch or sanitize unneutralized script content before it is served to users.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly target introduction of XSS via coding standards/testing (mostly), yet the single broad outcome leaves many specific neutralization vectors unaddressed (partial).

PR.PS-02 partial match
blocks

Patching and EOL replacement can remediate known XSS instances in libraries or frameworks (partial) but do nothing to enforce input neutralization in application code (none).

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Secure-coding testing and automated code-analysis tools are applied to detect improper neutralization of script-related content during web-page generation.

prevents

Secure-coding standards, SAST scans and removal of insecure code samples together eliminate the failure to neutralize script content that produces cross-site scripting flaws.

References