Quick answers
- Is CVE-2026-103900 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-103900 being exploited in the wild.
- How severe is CVE-2026-103900?
- High severity, with a CVSS score of 8.1, published 7 November 2026.
- Which products and versions are affected?
- WPJAM Basic up to and including 7.1.
- Is there a fix for CVE-2026-103900?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-103900 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-103900?
- Check whether you run WPJAM Basic at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in the WPJAM_User_Signup::signup() AJAX handler, which unpacks attacker-supplied data[args] parameters and merges them into user creation payload without proper validation of the role field. The role parameter bypasses the internal whitelist in WPJAM_User::create() and reaches wp_insert_user(), allowing privilege escalation. The endpoint is accessible to unauthenticated users (wp_ajax_nopriv) and only requires a nonce that is publicly available on the login page.
Affected products
- WPJAM WPJAM Basic up to and including 7.1
Timeline
- 2026-11-07: disclosed