dbcve.org
Wordpress Rest Api AuthenticationWordPress extension · Miniorange

CVE-2022-45073

HIGH · 8.8 CVSS v3.1 Published 2022-11-18
Fix available
A fix is available. Upgrade to after 2.4.0 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in REST API Authentication plugin <= 2.4.0 on 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

A Cross-Site Request Forgery (CSRF) vulnerability exists in the REST API Authentication plugin for WordPress versions 2.4.0 and below. This allows attackers to potentially trick authenticated administrators into performing unintended actions via malicious requests to the REST API Authentication endpoints.

MitigationUpdate the REST API Authentication plugin to a version newer than 2.4.0, or apply vendor-supplied patches if available. Ensure WordPress admin sessions are not reused across untrusted networks.

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
Wordpress Rest Api AuthenticationWordPress extension
Affected:<= 2.4.0

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Identify if Miniorange REST API Authentication plugin is installed
    Log into WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for 'Miniorange Wordpress Rest Api Authentication' or check the /wp-content/plugins/ directory for a folder containing 'miniorange-rest-api-authentication'
    Affected if The plugin is not found in the installed plugins list or plugin directory
  2. Determine the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find the Miniorange REST API Authentication plugin, and read the version number from the plugin description header; alternatively, inspect the plugin's main PHP file for the 'Version' header in the plugin comment block
    Affected if The displayed version number is 2.4.0 or lower
  3. Verify REST API Authentication endpoints are accessible
    Send a GET request to your WordPress site endpoint /wp-json/mo_api_authentication/v1/ or check the site's REST API routes using /wp-json/ to confirm authentication endpoints are exposed
    Affected if The REST API Authentication endpoints return a response rather than a 404 or authentication error
  4. Confirm WordPress administrator accounts exist
    Check WordPress users dashboard at /wp-admin/users.php or query the wp_users database table for users with the 'administrator' role
    Affected if There are active administrator-level user accounts in the WordPress installation
  5. Check for admin session activity
    Review active WordPress sessions or check browser cookies for logged-in administrator sessions; examine if admin sessions can be reused across different IP addresses or networks
    Affected if Administrator users have active sessions that could potentially be exploited via CSRF

You are affected if the Miniorange Wordpress Rest Api Authentication plugin is installed with version 2.4.0 or lower and the REST API Authentication endpoints are accessible to unauthenticated or low-privilege attackers.

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

Update the REST API Authentication plugin to a version newer than 2.4.0, or apply vendor-supplied patches if available. Ensure WordPress admin sessions are not reused across untrusted networks.

Recommended fix Moderate confidence

Version higher than 2.4.0 (check WordPress plugin repository for the latest secure release)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'REST API Authentication' plugin
  4. 4. Check the current version number displayed under the plugin name
  5. 5. If the installed version is 2.4.0 or lower, click 'Update Now' to install the latest available version
  6. 6. After updating, verify the plugin is functioning correctly by testing REST API authentication
Caveat Review plugin changelog for any breaking changes between your current version and the new version

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

Fix this in Wordpress Rest Api Authentication Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
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,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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