Quick answers
- Is CVE-2026-107625 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-107625 being exploited in the wild.
- How severe is CVE-2026-107625?
- Medium severity, with a CVSS score of 6.4, published 28 October 2026.
- Which products and versions are affected?
- Ultimate Member up to and including 2.14.0.
- Is there a fix for CVE-2026-107625?
- Yes: fixed in 2.14.1. Until then: Upgrade to version 2.14.1 or later. The fix adds a confirmation prompt for external links and improves input handling for the user_url parameter. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-107625 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-107625?
- Check whether you run Ultimate Member 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.
How to fix
- Fixed in: 2.14.1
Upgrade to version 2.14.1 or later. The fix adds a confirmation prompt for external links and improves input handling for the user_url parameter.
Technical details
Insufficient input sanitization and output escaping of the 'user_url' parameter allows authenticated attackers with subscriber-level access to inject stored XSS payloads. The vulnerability is made practical by a default redirect-confirmation onclick handler that triggers when users click the external link on a public profile. An attacker can store malicious JavaScript that executes in the context of any visitor viewing the compromised profile.
Affected products
- Ultimate Member Ultimate Member up to and including 2.14.0
Timeline
- 2026-10-28: disclosed
- 2026-10-21: patched