VariantBug

Finding a bug variant in CiviForm: same missing check, different route

Nguyen Thanh Tin — Independent security researcher, running VariantBug Advisory: GHSA-6w4r-8x7p-2hm5 · CWE-639 · CVSS 4.3 (Medium) · Fixed in CiviForm 3.36.0

Every public advisory is a map to the next bug. This one came from reading a patch.

Summary

CiviForm lets trusted intermediaries (TI) act on behalf of applicants. A previously disclosed advisory, GHSA-qv7c-9hjr-9rv7, described a route that performed the role check but not the ownership check. Reading that patch raised an obvious question: how many other routes share this authorization pattern, and are they all checked?

One wasn’t. GET /applicants/:applicantId/programs/:programName verified the requester was a TI or admin, but never verified the applicant belonged to them. Fixed in v3.36.0.

The variant angle

The original advisory did half the enumeration work for free:

  1. It named the bug class — act-on-behalf-of routes missing the applicant-ownership check.
  2. It listed which routes were already clean — the review and edit pages had the check.

So the candidate set was small: every route carrying :applicantId in its path, minus the ones the advisory said were safe. programs/:programName was left over. Reading its controller confirmed the shape: a role gate, no ownership gate — the same “check at the wrong layer” pattern as the original bug.

Applicant IDs are sequential, so enumeration was trivial: a TI for organization A could open the program page of any applicant served by organization B, and see their name, email, and program enrollments.

Impact — honestly rated

This is a Medium, and the advisory says so plainly: identity and enrollment details across organizations, not application answers; requires a TI account; CVSS 4.3. Nothing in the answers, no privilege escalation. I reported it as such and the vendor rated it the same way — which is how the process should work.

Takeaways

Timeline