Is CVE-2026-15212 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-15212 being exploited in the wild.

How severe is CVE-2026-15212?

High severity, with a CVSS score of 8.8, published 23 July 2026.

Which products and versions are affected?

WPO365 | Login up to, and including, 43.2.

Is there a fix for CVE-2026-15212?

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-15212 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-15212?

Check whether you run WPO365 | Login 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.

CVE-2026-15212: WPO365 Login CSRF in update_settings handler

CVE-2026-15212 · Severity: high · CVSS 8.8 · Published 2026-07-23

The WPO365 | Login plugin for WordPress, which integrates Microsoft services with WordPress sites, contains a security flaw that allows attackers to change the plugin's settings. By tricking a site administrator into clicking a malicious link, an attacker can gain administrative control over the website or modify user roles. This could lead to a full site takeover and unauthorized access to sensitive data.

Technologies: WPO365 | Login. Vendors: WPO365.

Quick answers

Is CVE-2026-15212 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-15212 being exploited in the wild.
How severe is CVE-2026-15212?: High severity, with a CVSS score of 8.8, published 23 July 2026.
Which products and versions are affected?: WPO365 | Login up to, and including, 43.2.
Is there a fix for CVE-2026-15212?: 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-15212 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-15212?: Check whether you run WPO365 | Login 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 WPO365 | Login plugin for WordPress is vulnerable to Cross-Site Request Forgery (CSRF) due to a failure in the Ajax_Service::verify_ajax_request() helper. The function gates its wp_verify_nonce() call behind an 'enable_nonce_check' option that is absent from the default configuration, causing it to evaluate to false. Consequently, the wp_ajax_wpo365_update_settings handler accepts cross-origin POST requests. An attacker can provide a base64/JSON 'settings' payload that is merged into the plugin's options without an allowlist. This allows an unauthenticated attacker to enable the SCIM REST endpoint, set a known secret token, and change the default user role to 'administrator' by inducing an authenticated administrator to interact with a malicious link.

Affected products

WPO365 WPO365 | Login up to, and including, 43.2

Timeline

2026-07-23: advisory: NVD publication date
2026-07-23: disclosed: Wordfence disclosure date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.