WP OAuth Server (OAuth Authentication) <= 4.2.1 - Authenticated (Administrator+) Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 4.2.2
- Affected Plugin
- WP OAuth Server (OAuth Authentication)
- Affected Version
<= 4.2.1- CVSS
- 5.5Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2022-3892
At a glance
CVE-2022-3892 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WP OAuth Server (OAuth Authentication) WordPress plugin, affecting versions <= 4.2.1. It carries a CVSS score of 5.5 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Administrator level or above. The issue is fixed in version 4.2.2; sites on affected versions should update now. Disclosed November 2022, reported by István Márton.
Vulnerability Overview
The WP OAuth Server plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the client ID parameter in versions up to, and including, 4.2.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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 interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in WP OAuth Server (OAuth Authentication) <= 4.2.1 takes an account at Administrator level or above. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For WP OAuth Server (OAuth Authentication) the fix is 4.2.2: builds <= 4.2.1 are affected, anything from 4.2.2 onward is not.
Remediation
Update to version 4.2.2, or a newer patched version
How does WordSec protect against this?
An attacker needs Administrator access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP OAuth Server (OAuth Authentication) 4.2.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in WP OAuth Server (OAuth Authentication)
- 9.8CVE-2015-9435: WP OAuth Server Pseudorandom Number Generation
CVE-2015-9435 - 8.8CVE-2022-3926: WP OAuth Server (OAuth Authentication) <= 4.2.5 CSRF
CVE-2022-3926 - 6.5CVE-2022-3894: WP OAuth Server CSRF
CVE-2022-3894 - 5.4CVE-2024-31253: OAuth Server <= 4.3.3 Open Redirect
CVE-2024-31253 - 5.4WP OAuth Server (OAuth Authentication) <= 4.2.5 CSRF
- 4.3CVE-2022-4148: WP OAuth Server Arbitrary Client Deletion
CVE-2022-4148
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C