Quick answers
- Is CVE-2026-104766 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-104766 being exploited in the wild.
- How severe is CVE-2026-104766?
- High severity, with a CVSS score of 8.8, published 10 October 2026.
- Which products and versions are affected?
- LatePoint up to and including 5.7.3.
- Is there a fix for CVE-2026-104766?
- 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-104766 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-104766?
- Check whether you run LatePoint 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 OsSettingsController::update() handler processes attacker-controlled settings parameters without an allowlist, and OsSettingsHelper::prepare_value() fails to validate the `default_wp_role_for_customer` setting server-side despite UI restrictions existing in the client. An authenticated LatePoint agent or custom role holding the `settings__edit` capability can inject `administrator` as the default role, escalating any subsequently registered customer to WordPress administrator. The vulnerability requires prior WordPress admin configuration granting `settings__edit` to the attacker's LatePoint role.
Affected products
- LatePoint LatePoint up to and including 5.7.3
Timeline
- 2026-10-10: disclosed