CVE-2026-15212: CWE-352 Cross-Site Request Forgery (CSRF) in wpo365 WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN)
The WPO365 | Login plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 43.2. This is due to the Ajax_Service::verify_ajax_request() helper gating its wp_verify_nonce() call behind the boolean option 'enable_nonce_check', which is absent from the default 'wpo365_options' array and therefore evaluates to false via get_global_boolean_var(); as a result, the wp_ajax_wpo365_update_settings handler (Ajax_Service::update_settings) accepts POSTs from cross-origin pages and forwards the attacker-supplied 'settings' payload (base64/JSON) to Options_Service::update_options(), which merges every key/value into wpo365_options without a key allowlist. This makes it possible for unauthenticated attackers to overwrite arbitrary plugin options — including enabling the SCIM REST endpoint (enable_scim), planting an attacker-known scim_secret_token, and setting new_usr_default_role to 'administrator' — via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
AI Analysis
Technical Summary
The WPO365 | Login plugin for WordPress is vulnerable to CSRF due to the Ajax_Service::verify_ajax_request() gating its wp_verify_nonce() call behind an option ('enable_nonce_check') that is absent from the default configuration and thus evaluates to false. Consequently, the wp_ajax_wpo365_update_settings AJAX handler accepts cross-origin POST requests without nonce verification. Attackers can supply a base64-encoded JSON 'settings' payload that is merged into the plugin's options without any key allowlist, allowing arbitrary option overwrites. This includes enabling the SCIM REST endpoint, planting attacker-controlled tokens, and setting the default new user role to administrator. Exploitation requires tricking a site administrator into performing an action such as clicking a crafted link.
Potential Impact
Successful exploitation allows unauthenticated attackers to perform unauthorized changes to plugin settings, potentially enabling backdoor access via the SCIM REST endpoint and elevating privileges by setting the default new user role to administrator. This can lead to full site compromise, including confidentiality, integrity, and availability impacts as reflected by the CVSS score of 8.8.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, administrators should avoid clicking on untrusted links and consider disabling or restricting access to the affected AJAX endpoint if possible. Monitor official vendor channels for updates and apply patches promptly once released.
CVE-2026-15212: CWE-352 Cross-Site Request Forgery (CSRF) in wpo365 WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN)
Description
The WPO365 | Login plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 43.2. This is due to the Ajax_Service::verify_ajax_request() helper gating its wp_verify_nonce() call behind the boolean option 'enable_nonce_check', which is absent from the default 'wpo365_options' array and therefore evaluates to false via get_global_boolean_var(); as a result, the wp_ajax_wpo365_update_settings handler (Ajax_Service::update_settings) accepts POSTs from cross-origin pages and forwards the attacker-supplied 'settings' payload (base64/JSON) to Options_Service::update_options(), which merges every key/value into wpo365_options without a key allowlist. This makes it possible for unauthenticated attackers to overwrite arbitrary plugin options — including enabling the SCIM REST endpoint (enable_scim), planting an attacker-known scim_secret_token, and setting new_usr_default_role to 'administrator' — via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
CVSS v3.1
Score 8.8high
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The WPO365 | Login plugin for WordPress is vulnerable to CSRF due to the Ajax_Service::verify_ajax_request() gating its wp_verify_nonce() call behind an option ('enable_nonce_check') that is absent from the default configuration and thus evaluates to false. Consequently, the wp_ajax_wpo365_update_settings AJAX handler accepts cross-origin POST requests without nonce verification. Attackers can supply a base64-encoded JSON 'settings' payload that is merged into the plugin's options without any key allowlist, allowing arbitrary option overwrites. This includes enabling the SCIM REST endpoint, planting attacker-controlled tokens, and setting the default new user role to administrator. Exploitation requires tricking a site administrator into performing an action such as clicking a crafted link.
Potential Impact
Successful exploitation allows unauthenticated attackers to perform unauthorized changes to plugin settings, potentially enabling backdoor access via the SCIM REST endpoint and elevating privileges by setting the default new user role to administrator. This can lead to full site compromise, including confidentiality, integrity, and availability impacts as reflected by the CVSS score of 8.8.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, administrators should avoid clicking on untrusted links and consider disabling or restricting access to the affected AJAX endpoint if possible. Monitor official vendor channels for updates and apply patches promptly once released.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-07-09T07:43:41.039Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a62711c9c2644c7f89e06e2
Added to database: 07/23/2026, 19:53:00 UTC
Last enriched: 07/23/2026, 20:07:08 UTC
Last updated: 07/24/2026, 03:43:27 UTC
Views: 13
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.