dbcve.org
Wp Oauth ServerWordPress extension · Miniorange

CVE-2022-34149

CRITICAL · 9.8 CVSS v3.1 Published 2022-08-22
Fix available
A fix is available. Upgrade to after 3.0.4 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 miniOrange WP OAuth Server plugin <= 3.0.4 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

The miniOrange WP OAuth Server plugin for WordPress versions 3.0.4 and below contains an authentication bypass vulnerability that allows attackers to bypass authentication mechanisms and gain unauthorized access to the WordPress site, likely through improper validation in the OAuth authentication flow.

MitigationUpdate the miniOrange WP OAuth Server plugin to a version newer than 3.0.4 immediately. Review authentication logs for unauthorized access attempts and consider resetting user credentials as a precautionary measure.

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 Oauth ServerWordPress extension
Affected:<= 3.0.4

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. Check if miniOrange WP OAuth Server plugin is installed
    In WordPress admin dashboard, go to Plugins > Installed Plugins and look for 'miniOrange WP OAuth Server' or check the wp-content/plugins directory for the oauth-server folder
    Affected if The plugin is present in the WordPress installation
  2. Determine the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find the miniOrange WP OAuth Server plugin, and note the version number displayed below the plugin name. Alternatively, check the main plugin file (oauth-server.php) for the 'Version' header in the plugin comments
    Affected if The version is 3.0.4 or lower (any version <= 3.0.4)
  3. Verify OAuth Server functionality is enabled
    Navigate to WordPress admin > OAuth Server > App/Client settings (or similar menu path depending on plugin UI) and check if any OAuth server endpoints are active or if any clients are configured
    Affected if OAuth server endpoints are configured and active, making the authentication flow vulnerable to exploitation
  4. Review authentication logs for suspicious OAuth activity
    Check WordPress debug logs (wp-content/debug.log), server access logs, and any OAuth-specific logs for unauthorized access patterns, unexpected OAuth token usage, or login anomalies around the time of potential exploitation
    Affected if Logs show OAuth-based logins from unknown users or IPs that were not initiated through normal WordPress authentication

A user is affected if the miniOrange WP OAuth Server plugin version is 3.0.4 or lower AND the OAuth server functionality is enabled in their WordPress environment.

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 3.0.4
Interim mitigation

Update the miniOrange WP OAuth Server plugin to a version newer than 3.0.4 immediately. Review authentication logs for unauthorized access attempts and consider resetting user credentials as a precautionary measure.

Recommended fix High confidence

Version 3.0.5 or later of miniOrange WP OAuth Server plugin

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'WP OAuth Server' (miniOrange) in the plugin list
  4. Click 'Update now' if an update is available, or manually update to version 3.0.5 or higher
  5. After updating, verify the plugin version shows 3.0.5 or later in the plugins list
  6. Test OAuth authentication flow to confirm the vulnerability is remediated
Caveat Review plugin settings after upgrade as minor updates may include configuration changes

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

Fix this in Wp Oauth Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
5.0 hours of engineering $880
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-34149 — 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-34149 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