CVE-2026-18345: WP User Manager – User Profile Builder & Membership · Missing Authorization
Affects WP User Manager – User Profile Builder & MembershipSource CVE Database V5
Not known to be exploited · CVSS 4.3 Medium.
Data as of 5 Nov 2026, 23:24 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 22 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| wpusermanagerWP User Manager – User Profile Builder & Membership | Affected
| Fixed in– |
AI-suggested
Until a fix is available, restrict access to /wp-admin/ to trusted users only and monitor for suspicious Stripe OAuth activity. Avoid granting Subscriber or higher roles to untrusted users.
Description
The WP User Manager plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the Connect::complete() function in versions up to, and including, 2.9.18. The function is registered on the admin_init hook (which fires for every authenticated user that reaches /wp-admin/, including Subscribers) and performs no current_user_can() or nonce verification before fetching Stripe credentials from the external WPUM connect service and writing them (publishable key, secret key, gateway mode, and connected Stripe account ID) into the wpum_settings option via wpum_update_option()/update_option(). This makes it possible for authenticated attackers, with Subscriber-level access and above, to hijack the site's Stripe integration by completing their own Stripe Connect OAuth flow and then invoking the callback on the target site, causing all subsequent Stripe payments to be routed to the attacker's Stripe account.
References
- wordfence.com/threat-intel/vulnerabilities/id/ecae11ec-c952-4f5a-9e55-e2ac2fa05100?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-user-manager/tags/2.9.18/includes/integrations/stripe/Connect.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-user-manager/tags/2.9.18/includes/integrations/stripe/Connect.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-user-manager/tags/2.9.18/includes/integrations/stripe/Connect.php (opens in a new tab)
- plugins.trac.wordpress.org/changeset?reponame=&old=3701837%40wp-user-manager&new=3701837%40wp-user-manager (opens in a new tab)