vulns.co
/
GKData.io MCP and API Buy me a coffee

HotCRP

HotCRP: separate submission visibility from authorship authority

HotCRP allowed permission to view a submission to extend to changing its contact authorship. The maintainer reports that reviewers and program-committee members could gain author-level access to submissions they could already see. This affected submission anonymity and integrity.

Open the referenceMaintainer AdvisoryReviewed 2026-10-03

How to use this reference

Editorial lesson: authority-changing metadata needs its own permission check; visibility alone must not authorize membership changes. The advisory identifies versions 3.0.0–3.3.1 as affected and 3.4 as fixed. Release notes date 3.4 to August 5, before disclosure on August 11.

Before reading

  • Basic server-side identity and authorization concepts

Context and limits

  • Requires an authenticated reviewer or program-committee member and existing submission visibility; this is not an unauthenticated access claim.
  • The maintainer reports an action-log review finding no exploitation on its hosted service. That statement does not establish absence of incidents in other deployments. The advisory reports capability and consequences, without a separate production-incident narrative.
  • kohler published the advisory; discovery is credited to an internal audit without a named individual reporter. The original report date is unknown.
  • This review did not independently verify the patch implementation or deployed state. Upgrade evidence does not establish reversal of any prior unauthorized authorship changes. Learning prerequisites are editorial.

Sources

  1. Escalation to author access by reviewersHotCRP · reviewed 2026-10-03
  2. HotCRP release notes: version 3.4HotCRP · reviewed 2026-10-03

Record reviewed 2026-10-03. Snapshot af2809c308fc. Open the complete JSON contract.

Library synced 2026-11-18 · cases last reviewed 2026-10-05

af2809c308fc · JSON exports & schemas · CC BY 4.0 content / MIT software