dbcve.org
Wp Oauth2 ServerWordPress extension · Codexshaper

CVE-2022-34839

CRITICAL · 9.8 CVSS v3.1 Published 2022-07-22
Fix available
A fix is available. Upgrade to after 1.0.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Authentication Bypass vulnerability in CodexShaper's WP OAuth2 Server plugin <= 1.0.1 at WordPress.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Authentication bypass vulnerability in CodexShaper's WP OAuth2 Server plugin for WordPress versions 1.0.1 and below allows attackers to bypass authentication mechanisms, potentially gaining unauthorized access to the OAuth2 server functionality and protected resources.

MitigationUpdate the WP OAuth2 Server plugin to the latest patched version immediately. Review access logs for unauthorized OAuth2 token generation or resource access attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wp Oauth2 ServerWordPress extension
Affected:<= 1.0.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify WP OAuth2 Server plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP OAuth2 Server' by CodexShaper, or check the plugins directory at /wp-content/plugins/ for a folder named 'wp-oauth2-server' or similar CodexShaper OAuth folder.
    Affected if The plugin is present on the WordPress installation
  2. Check installed plugin version
    In WordPress admin Plugins page, click on the plugin to view details and find the version number, or read the main plugin PHP file header for 'Version:' tag in /wp-content/plugins/[oauth-plugin-folder]/index.php
    Affected if Version is 1.0.1 or lower
  3. Confirm OAuth2 server endpoint is publicly accessible
    Check the site's robots.txt or manually access the OAuth2 authorization endpoint typically at /oauth/authorize or /wp-json/oauth/v1/authorize to verify the endpoint responds.
    Affected if The OAuth2 authorization endpoint responds and is accessible without authentication
  4. Review access logs for unauthorized token requests
    Examine web server access logs (Apache error/access logs or Nginx access logs) for repeated POST requests to /oauth/token or /wp-json/oauth/v1/token endpoints, especially with varying client credentials.
    Affected if There are unexpected or unauthorized OAuth2 token generation attempts from unfamiliar IP addresses

If the CodexShaper WP OAuth2 Server plugin version 1.0.1 or lower is installed and the OAuth2 endpoints are publicly accessible, the environment is affected by this authentication bypass vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 1.0.1
Interim mitigation

Update the WP OAuth2 Server plugin to the latest patched version immediately. Review access logs for unauthorized OAuth2 token generation or resource access attempts.

Recommended fix High confidence

Version 1.0.2 or latest available version on wordpress.org

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'WP OAuth2 Server' (or 'CodexShaper WP OAuth2 Server') plugin
  4. Click 'Update now' if an update is available, or manually download and install the latest version from wordpress.org
  5. Verify the updated version number is 1.0.2 or higher
  6. Test OAuth2 authentication flow to confirm functionality works correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wp Oauth2 Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-34839 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-34839 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data