
WPMgr v0.61.199 High 8.1 Remote OAuth leftover. A self-serve planted password on a victim email survives verify and Google/GitHub/OIDC link. Attacker then logs in as the victim.
Someone who knows your email can register it first, set a password you never chose, and wait. When you later click the verification mail and sign in with Google or GitHub, WPMgr links that identity onto the planted row and leaves the attacker's password in place. They then log in as you with the password they picked. This is after the install is claimed. It needs you to verify the address. It does not need them inside your mailbox if you click the mail yourself.
Class: OAuth leftover (account linking) Reach: Remote (self-serve registrant after claim; victim verifies email)
WPMgr v0.61.199 (e1b3a163) - mosamlife
| ID | no CVE yet |
| Class | OAuth leftover (social link onto a planted password) |
| Reach | Remote (untrusted self-serve after the install is claimed) |
| CWE | CWE-287 / CWE-284 |
| CVSS | High: 8.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N |
| Product | WPMgr |
| Affected | v0.61.199 (e1b3a163988c9f1c31bc93922ea34322fa188792) |
| Auth | none to plant. Victim clicks the verification mail. Later victim SSO. |
| License | GNU Affero GPL v3.0 |
| Lab | loopback 127.0.0.1:18180-18186. Compose wpmgrh04. |
Needs an install that already has an owner (self-serve is open after claim) and the victim's email address. The victim has to verify that address. SSO-only rows with an empty password_hash are a different story.
| Privilege | Method / sink | Recon / integrity / availability | Lab-proven or inferred |
|---|---|---|---|
| Plant a pending user with an attacker-chosen argon2 password | POST /auth/register for the victim email | Integrity (account plant) | Lab-proven. Row pending|hash|unverified |
| Mail a verification token for that planted row | unauthenticated ResendVerification / register mail | Recon (token in mail) | Lab-proven. Mailpit captured verify-email?token= |
| Activate the planted row without clearing the hash | POST /auth/verify-email → MarkUserEmailVerified | Integrity | Lab-proven. Row active|hash|verified |
| Bind Google / GitHub / OIDC onto that same row | GET /auth/oidc/callback → CompleteSocialLink | Integrity (identity link) | Lab-proven. oidc|[email protected] |
| Sign in as the victim with the planted password after SSO | POST /auth/login email + attacker password | Integrity (session as victim) | Lab-proven. wpmgr_session, identities still show oidc |
| Negative control: plant without verify | OIDC start on a pending row | n/a | Source. socialStatusGate returns email_not_verified |
Stays closed on this leftover
| Axis | Method / sink | Why it is closed |
|---|---|---|
| Integrity | SSO-only victim with empty password_hash | No planted hash to keep. Out of class |
| Integrity | MCP OAuth register / token / consent | PKCE S256, exact redirect, consent behind PermAPIKeyManage |
| Integrity | Unclaimed first-run | Bootstrap claim still required before self-serve |
| Integrity | Password reset as a session mint | Reset does not issue wpmgr_session |
I ran this as a loopback compose with Dex standing in for Google. The interesting bit was not the plant. It was MarkUserEmailVerified leaving password_hash alone, so the SSO link never converted the row to social-only.
Pin mosamlife/wpmgr tag v0.61.199. decideSocial already names this pre-hijack and refuses to link until the address is verified. The pending gate fires first, so the dashboard copy that would tell the victim to reset a password they did not set never shows. Verify only flips email_verified_at and status=active. The next OIDC callback hits socialLinkExisting.
Wrong turns: treating MCP OAuth open client registration as this leftover (it is bounded to a row); treating SSO-only empty-hash accounts as in scope.
python3 wpmgr-social-planted-password-Abraxas-Labs.py
or:
cd lab
./run.sh
Clones mosamlife/wpmgr at e1b3a163 into lab/src, builds wpmgr-lab:v0.61.199 / wpmgr-lab-web:v0.61.199 if missing, and talks to loopback. Docker, python3, git. Mailpit sits on 1.2.3.0/24 because the product SMTP dialer refuses RFC1918 and loopback.
IOC planted-pending pending|hash|unverified
IOC email-verified-hash-kept active|hash|verified
IOC oidc-linked oidc|[email protected]
IOC password-login-survived active|hash|verified oidc|[email protected]
SUCCESS WPMGR-H04-SOCIAL-PLANT planted-password-survives-oidc-link WPMGR-H04-PLANTED-PASSWORD-SURVIVES
On verify, and again in CompleteSocialLink, clear password_hash (or force a reset) when the row was never used for a password login the owner chose. Do not link a provider onto a hash the current user did not set. Show the reset copy on the pending path, not only after a status that never happens.
e1b3a163988c9f1c31bc93922ea34322fa188792decideSocial / CompleteSocialLinkMarkUserEmailVerifiedGNU Affero GPL v3.0. See LICENSE. Loopback lab only. No warranty.
Abraxas Labs [email protected]