Security Resilience

CVE-2026-23836

Hotcrp 3.0 – 3.2

Published
19 January 2026
Modified
18 February 2026
Patch / advisory
CVSS Score v3.1 9.9
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS Score 0.0046 39th percentile
Risk Priority 68 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-23836 is a critical-severity Improper Input Validation (CWE-20) vulnerability in Hotcrp. Its CVSS base score is 9.9 (Critical).

Operationally, ranked at the 39th 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-23836 is a critical vulnerability in HotCRP, an open-source conference review software, stemming from inadequately sanitized code generation for HotCRP formulas. Introduced in version 3.1 in April 2024, the flaw (classified under CWE-20: Improper Input Validation) enables the execution of arbitrary PHP code. It carries a CVSS v3.1 base score of 9.9, reflecting its network accessibility, low attack complexity, low required privileges, lack of user interaction, scope change, and high impacts on confidentiality, integrity, and availability.

Low-privileged users (PR:L) with network access (AV:N) can exploit this vulnerability without user interaction (UI:N). Successful exploitation allows attackers to execute arbitrary PHP code on the server, potentially leading to full system compromise, data exfiltration, modification of conference data, or further lateral movement given the scope change (S:C) and high impact ratings (C:H/I:H/A:H).

The GitHub security advisory (GHSA-hpqh-j6qx-x57h) and related commits detail the patch in HotCRP release version 3.2, which addresses the sanitization issue in formula code generation. Security practitioners should upgrade to version 3.2 or later and review access controls for formula usage in affected deployments.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

HotCRP is conference review software. A problem introduced in April 2024 in version 3.1 led to inadequately sanitized code generation for HotCRP formulas which allowed users to trigger the execution of arbitrary PHP code. The problem is patched in release…

more

version 3.2.

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-23878Same product: Hotcrp Hotcrp
CVE-2026-25156Same product: Hotcrp Hotcrp
CVE-2023-25951Shared CWE-20
CVE-2026-7953Shared CWE-20
CVE-2023-29359Shared CWE-20
CVE-2024-38189Shared CWE-20
CVE-2025-9467Shared CWE-20
CVE-2026-4987Shared CWE-20
CVE-2026-17844Shared CWE-20
CVE-2025-27517Shared CWE-20

Affected Assets

hotcrp
hotcrp
3.0 — 3.2

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover missing input validation through analysis or test cases.

SI-10 directly requires validity checks on information inputs, structurally preventing improper or missing validation.

Requiring documented development standards and tools can embed input-validation practices into the engineering process.

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

Testing against a defined set of requirements and using code review plus vulnerability scanning forces validation of inputs and handling of unanticipated conditions, reducing the chance that malformed data will be accepted.

prevents

Requiring language-specific secure coding standards, peer review, SAST and documented mitigation of common programming errors forces validation of all inputs before they are trusted.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-20, a class-level weakness, and none of its children carries one either.

References