OAuth Single Sign On – SSO (OAuth Client) <= 6.24.1 - Cross-Site Request Forgery via 'delete' in mooauth_client_applist_page
Strategic Overview
- Status
- Patched in 6.24.2
- Affected Plugin
- OAuth Single Sign On – SSO (OAuth Client)
- Affected Version
<= 6.24.1- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2023-1092
At a glance
CVE-2023-1092 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the OAuth Single Sign On WordPress plugin, affecting versions <= 6.24.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 6.24.2; sites on affected versions should update now. Disclosed February 2023, reported by Nguyen Thuc Tuyen.
Vulnerability Overview
The OAuth Single Sign On – SSO (OAuth Client) plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 6.24.1. This is due to missing or incorrect nonce validation on the 'delete' case in the mooauth_client_applist_page function. This makes it possible for unauthenticated attackers to make changes to the configured apps via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
OAuth Single Sign On <= 6.24.1 carries this weakness at delete, and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For OAuth Single Sign On the fix is 6.24.2: builds <= 6.24.1 are affected, anything from 6.24.2 onward is not.
Remediation
Update to version 6.24.2, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to OAuth Single Sign On: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: OAuth Single Sign On 6.24.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in OAuth Single Sign On – SSO (OAuth Client)
- 9.8CVE-2025-9485: OAuth Single Sign On – SSO Authentication Bypass
CVE-2025-9485 - 8.8CVE-2022-34155: OAuth Single Sign On – SSO Missing Authorization
CVE-2022-34155 - 8.1CVE-2024-10111: OAuth Single Sign On – SSO Authentication Bypass
CVE-2024-10111 - 8.1CVE-2022-2133: OAuth Single Sign On – SSO Authentication Bypass
CVE-2022-2133 - 6.4OAuth Single Sign On – SSO (OAuth Client) <= 6.22.5 XSS
- 6.1Multiple miniOrange Plugins (Various Version) Reflected XSS
- 5.3CVE-2025-10753: OAuth Single Sign On – SSO Missing Authorization
CVE-2025-10753
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C