{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-18345 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-18345 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-18345 is a medium-severity missing authorization vulnerability in wpusermanager WP User Manager – User Profile Builder \u0026 Membership, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-18345 and fix it if it is affected.\n\nWhat it is: CVE-2026-18345 is a medium-severity missing authorization vulnerability in wpusermanager WP User Manager – User Profile Builder \u0026 Membership, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-18345 in the wild and no public exploit code.\n\nAffected product: wpusermanager WP User Manager – User Profile Builder \u0026 Membership. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-18345/ (Markdown: https://insights.sbomify.com/CVE-2026-18345/index.md)","id":"CVE-2026-18345","markdown":"https://insights.sbomify.com/CVE-2026-18345/index.md","name":"CVE-2026-18345","record":{"aliases":["GHSA-9596-j6mw-33fx"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated subscribers can hijack Stripe integration by exploiting missing authorization checks in the callback function, redirecting payments to their own accounts.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Missing authorization in WP User Manager – User Profile Builder \u0026 Membership","id":"CVE-2026-18345","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"TikTok \u003c= 1.4.1 - Missing Authorization to Unauthenticated TikTok Integration Takeover via 'auth_code' Parameter","id":"CVE-2026-18346"},"packages":[],"prev":{"headline":"Responsive Thumbnail Slider \u003c 1.1.53 - Reflected Cross-Site Scripting via 'id' Parameter","id":"CVE-2026-18344"},"products":["WP User Manager – User Profile Builder \u0026 Membership"],"published":"2026-09-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-22","vendors":["wpusermanager"]},"summary":"Authenticated subscribers can hijack Stripe integration by exploiting missing authorization checks in the callback function, redirecting payments to their own accounts.","url":"https://insights.sbomify.com/CVE-2026-18345/"}