Check the required conditions.
Check your setup, then review each finding separately. The four findings have different requirements.
- Do we use WPMgr 0.61.199?Confirm the installed version and whether the dashboard is hosted or self-hosted.
- Which sign-in and invitation features are in use?Review 2FA, single sign-on and canceled client invitations against the individual findings.
- Is it self-hosted?Check dashboard and Dex access, and whether the shipped account remains unchanged.
If you use WPMgr and a finding’s conditions are present or unknown, ask the owner to check internal records and confirm remediation with the vendor.
Today
- Confirm whether it applies. Record version and hosting model. Check the conditions for each finding separately.
- Reduce the exposure. Restrict outside access to the dashboard. For self-hosted deployments, restrict Dex and replace the shipped account.
- Review the records. Preserve logs. Review new sessions, organizations and canceled invitations.
- Respond if you find unauthorized access. End affected sessions and start incident response.
Tomorrow
- Keep the evidence. Record the version, hosting model, relevant account conditions and log-review results.
- Complete the follow-up. Ask the vendor which deployments are affected and which versions contain fixes. The cited research identifies no verified fixed release.
- Confirm the result. Apply verified fixes. Review permissions, settings and backups.
Check your own records.
- Use your approved AI tool.
- Require evidence. Flag unknowns.
Read the prompt
Four reported findings
The linked researcher notes publish a separate CVSS 3.1 estimate for each finding. These are researcher estimates, not assigned-CVE scores or one combined rating. Notes and vendor release history checked November 13, 2026.
1. 2FA bypass
Source →- Required conditions
- User’s password + 2FA + attacker’s organization on the same installation.
- Reported outcome
- Session as victim without the second factor.
- Researcher CVSS 3.1 estimate
- 8.1 High. Abraxas Labs estimate for this finding.
2. Retained password
Source →- Required conditions
- Prior registration of the user’s email; user verifies it and links SSO.
- Reported outcome
- Risk: the retained password can grant account access.
- Researcher CVSS 3.1 estimate
- 8.1 High. Abraxas Labs estimate for this finding.
3. Shipped Dex account
Source →- Required conditions
- Self-hosted, shipped account unchanged after setup; dashboard and Dex reachable.
- Reported outcome
- Shown: creation of a new organization. Takeover of an existing organization is unproven. The reports do not confirm whether the hosted service uses this setup.
- Researcher CVSS 3.1 estimate
- 9.8 Critical. Abraxas Labs estimate for this finding.
4. Canceled invitation
Source →- Required conditions
- Possession of a canceled client invitation.
- Reported outcome
- Acceptance grants membership and a session.
- Researcher CVSS 3.1 estimate
- 7.5 High. Abraxas Labs estimate for this finding.
Fix guidance
- The cited research identifies no verified fixed release. Ask the vendor for affected deployments and fixed versions.
- Check the installed version and hosting model against vendor guidance. The four findings have different account and invitation conditions.
- Apply verified fixes and review permissions, settings and backups. Record current remediation separately from any earlier exposure or evidence of unauthorized access.
What IntegrityLab.ai can check
- Supported page checks can report a reachable administration or login page within the agreed scope.
- That observation does not establish the WPMgr version, invitation behavior, 2FA bypass or a working shipped account.
- Confirm the current assessor scope. Use internal records and vendor guidance to confirm the required conditions and whether a reported finding applies.