What is the severity of CVE-2022-3926?

The severity of CVE-2022-3926 is considered high due to the potential for attackers to compromise admin secrets.

How do I fix CVE-2022-3926?

To fix CVE-2022-3926, update the WP OAuth Server plugin to version 3.4.2 or later.

What versions of the WP OAuth Server plugin are affected by CVE-2022-3926?

CVE-2022-3926 affects all versions of the WP OAuth Server plugin before 3.4.2.

What type of attack can CVE-2022-3926 enable?

CVE-2022-3926 can enable attackers to force logged-in admins to regenerate OAuth client secrets.

Is user authentication at risk due to CVE-2022-3926?

Yes, CVE-2022-3926 poses a risk to user authentication by allowing attackers to manipulate secret regeneration.

Vulnerability/
CVE-2022-3926

medium

6.5

CWE

352

5/12/2022

3/8/2024

CVE-2022-3926: WP OAuth Server < 3.4.2 - Client Secret Regeneration via CSRF

First published: Mon Dec 05 2022(Updated: )

The WP OAuth Server (OAuth Authentication) WordPress plugin before 3.4.2 does not have CSRF check when regenerating secrets, which could allow attackers to make logged in admins regenerate the secret of an arbitrary client given they know the client ID

Credit: contact@wpscan.com

Affected Software	Affected Version	How to fix
WP OAuth Server	<3.4.2

Never miss a vulnerability like this again

Reference Links

https://wpscan.com/vulnerability/e1fcde2a-91a5-40cb-876b-884f01c80336

Frequently Asked Questions

What is the severity of CVE-2022-3926?
The severity of CVE-2022-3926 is considered high due to the potential for attackers to compromise admin secrets.
How do I fix CVE-2022-3926?
To fix CVE-2022-3926, update the WP OAuth Server plugin to version 3.4.2 or later.
What versions of the WP OAuth Server plugin are affected by CVE-2022-3926?
CVE-2022-3926 affects all versions of the WP OAuth Server plugin before 3.4.2.
What type of attack can CVE-2022-3926 enable?
CVE-2022-3926 can enable attackers to force logged-in admins to regenerate OAuth client secrets.
Is user authentication at risk due to CVE-2022-3926?
Yes, CVE-2022-3926 poses a risk to user authentication by allowing attackers to manipulate secret regeneration.

agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/references
agent/author
agent/last-modified-date
agent/severity
agent/title
agent/weakness
agent/type
agent/description
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/wp-oauth
canonical/wp oauth server

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2022-3926?
The severity of CVE-2022-3926 is considered high due to the potential for attackers to compromise admin secrets.
How do I fix CVE-2022-3926?
To fix CVE-2022-3926, update the WP OAuth Server plugin to version 3.4.2 or later.
What versions of the WP OAuth Server plugin are affected by CVE-2022-3926?
CVE-2022-3926 affects all versions of the WP OAuth Server plugin before 3.4.2.
What type of attack can CVE-2022-3926 enable?
CVE-2022-3926 can enable attackers to force logged-in admins to regenerate OAuth client secrets.
Is user authentication at risk due to CVE-2022-3926?
Yes, CVE-2022-3926 poses a risk to user authentication by allowing attackers to manipulate secret regeneration.