
WPMgr v0.61.199 High 7.5 Remote broken revoke. A client invite token still accepts after DELETE revoke returns 204. The holder joins the client and gets a session.
You send a client invite, then change your mind and revoke it. The link is supposed to die. On this pin it does not. Anyone who still has the token can accept after the revoke returns 204, join the client, and get a session. This is not a tight race you have to win on the clock. Revoke first, accept second, both succeed.
Class: Auth leftover (broken revoke / single-use) Reach: Remote (holder of a still-pending client invite token)
WPMgr v0.61.199 (e1b3a163) - mosamlife
| ID | no CVE yet |
| Class | Auth leftover (invite accept after revoke) |
| Reach | Remote (anonymous token holder) |
| CWE | CWE-284 / CWE-367 |
| CVSS | High: 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| Product | WPMgr |
| Affected | v0.61.199 (e1b3a163988c9f1c31bc93922ea34322fa188792) |
| Auth | invite token only. No session. |
| License | GNU Affero GPL v3.0 |
| Lab | loopback 127.0.0.1:18200-18204. Compose wpmgrh12. |
Needs a client invitation token that was issued and then revoked. Org invitations have no revoke on this pin, so the lab used client invitations and no WordPress agent.
| Privilege | Method / sink | Recon / integrity / availability | Lab-proven or inferred |
|---|---|---|---|
| Accept after a committed revoke | DELETE /api/v1/clients/{id}/invitations/{invitation} 204, then POST /api/v1/invitations/accept 200 | Integrity (membership) | Lab-proven. Trial 2, 30ms. Both revoked_at and accepted_at set |
| Session as the new member | accept Set-Cookie: wpmgr_session | Integrity (authn) | Lab-proven |
| Client membership row | client_members count 2 | Integrity | Lab-proven |
| Negative control: revoke after a won accept | trial 1 accept 200, revoke 409 invitation_not_pending | n/a | Lab-proven. Expected CAS on the late revoke |
Stays closed on this leftover
| Axis | Method / sink | Why it is closed |
|---|---|---|
| Integrity | Double-accept of the same invite | FIX 5. Second claim invitation_already_used |
| Integrity | Enrollment pairing consume | compare-and-set |
| Integrity | Autologin consume | compare-and-set |
| Integrity | CP recovery codes | compare-and-set |
| Integrity | Org-invite revoke | No revoke API on this pin. Out of this leftover |
MarkInvitationAccepted updates WHERE id = $1 AND accepted_at IS NULL. It never asks revoked_at IS NULL and it never rebinds token_hash. Go checks those things earlier, in a different transaction, after looking the row up with no FOR UPDATE.
I went looking for a race. The lab won on a sequential revoke-then-accept. That is worse than TOCTOU. Comments in Service.Accept say a revoked invite is dead even to the original link. The SQL does not agree.
Wrong turns: needing a WordPress agent for client invites (the control plane will issue them without one); treating org invites as the revoke surface (they have none here).
python3 wpmgr-invite-accept-after-revoke-Abraxas-Labs.py
or:
cd lab
./run.sh
Clones mosamlife/wpmgr at e1b3a163 into lab/src. Loopback only.
IOC trial=2 revoke=204 accept=200
accepted_at=2026-11-09 22:05:33.960446+00
revoked_at=2026-11-09 22:05:33.944943+00
members=2 session_cookie=1
SUCCESS WPMGR-H12-INVITE-RACE trial=2 delay_ms=30 ... WPMGR-H12-ACCEPT-AFTER-REVOKE
Put revoked_at IS NULL and the presented token_hash in the same UPDATE that stamps accepted_at. Look the row up FOR UPDATE inside that transaction. Treat a row with both timestamps as a failed revoke, not a member.
e1b3a163988c9f1c31bc93922ea34322fa188792MarkInvitationAcceptedinvitation.Service.AcceptGNU Affero GPL v3.0. See LICENSE. Loopback lab only. No warranty.
Abraxas Labs [email protected]