Page MenuHomePhabricator

Require CSRF submission to verify email addresses
ClosedPublic

Authored by epriestley on Feb 26 2014, 3:55 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Jun 25, 12:29 AM
Unknown Object (File)
Apr 16 2026, 7:00 PM
Unknown Object (File)
Apr 15 2026, 6:39 PM
Unknown Object (File)
Mar 16 2026, 12:16 AM
Unknown Object (File)
Feb 17 2026, 3:58 AM
Unknown Object (File)
Dec 23 2025, 12:32 AM
Unknown Object (File)
Dec 4 2025, 1:35 PM
Unknown Object (File)
Nov 13 2025, 6:10 AM
Subscribers

Details

Summary

If an attacker somehow intercepts a verification URL for an email address, they can hypothetically CSRF the account owner into verifying it. What you'd do before (how do you get the link?) and after (why do you care that you tricked them into verifying) performing this attack is unclear, but in theory we should require a CSRF submission here; add one.

Test Plan

{F118691}

Diff Detail

Repository
rP Phabricator
Branch
csrfverify
Lint
Lint Passed
Unit
No Test Coverage