Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
wpmgr-invite-accept-after-revoke — 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. | Kitploit
Tools/GitHubGitHub/abraxas/wpmgr-invite-accept-after-revoke
Authentication & AuthorizationVulnerability AnalysisExploitationWeb SecurityPenetration TestingLabs & Practice
GitHubabraxas/wpmgr-invite-accept-after-revoke

wpmgr-invite-accept-after-revoke

Share

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.

View Repository
9 days agoNot yet reviewed

Abraxas Labs - wpmgr-invite-accept-after-revoke

wpmgr-invite-accept-after-revoke

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

IDno CVE yet
ClassAuth leftover (invite accept after revoke)
ReachRemote (anonymous token holder)
CWECWE-284 / CWE-367
CVSSHigh: 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
ProductWPMgr
Affectedv0.61.199 (e1b3a163988c9f1c31bc93922ea34322fa188792)
Authinvite token only. No session.
LicenseGNU Affero GPL v3.0
Labloopback 127.0.0.1:18200-18204. Compose wpmgrh12.

What an attacker can do

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.

PrivilegeMethod / sinkRecon / integrity / availabilityLab-proven or inferred
Accept after a committed revokeDELETE /api/v1/clients/{id}/invitations/{invitation} 204, then POST /api/v1/invitations/accept 200Integrity (membership)Lab-proven. Trial 2, 30ms. Both revoked_at and accepted_at set
Session as the new memberaccept Set-Cookie: wpmgr_sessionIntegrity (authn)Lab-proven
Client membership rowclient_members count 2IntegrityLab-proven
Negative control: revoke after a won accepttrial 1 accept 200, revoke 409 invitation_not_pendingn/aLab-proven. Expected CAS on the late revoke

Stays closed on this leftover

AxisMethod / sinkWhy it is closed
IntegrityDouble-accept of the same inviteFIX 5. Second claim invitation_already_used
IntegrityEnrollment pairing consumecompare-and-set
IntegrityAutologin consumecompare-and-set
IntegrityCP recovery codescompare-and-set
IntegrityOrg-invite revokeNo 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.

How I found it

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).

Lab

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

The fix

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.

References

  • github.com/mosamlife/wpmgr e1b3a163988c9f1c31bc93922ea34322fa188792
  • MarkInvitationAccepted
  • invitation.Service.Accept
  • CWE-284 · CWE-367

License

GNU Affero GPL v3.0. See LICENSE. Loopback lab only. No warranty.

Abraxas Labs [email protected]

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    867
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    544
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    385
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    360
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    302
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    279

Explore all tools

Browse our collection of tools

View all tools →