dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-39545

MEDIUM · 5.4 CVSS v3.1 Published 2025-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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
Missing Authorization vulnerability in miniOrange WordPress REST API Authentication wp-rest-api-authentication allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WordPress REST API Authentication: from n/a through <= 3.6.3.

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 WordPress REST API Authentication plugin versions through 3.6.3 contain a missing authorization vulnerability allowing attackers to exploit incorrectly configured access control security levels. This enables unauthorized access to the WordPress REST API due to improper validation of user permissions when security levels are misconfigured.

MitigationReview and correctly configure the plugin's access control security level settings, ensure proper authorization checks are enforced for all REST API endpoints, and update to the latest plugin version if available.

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

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

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

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 plugin installation and version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Locate 'miniOrange REST API Authentication' and note the version number displayed. Alternatively, check the plugin header in wp-content/plugins/miniorange-rest-api-authentication/readme.txt for the Version field.
    Affected if Installed version is 3.6.3 or lower (any version through 3.6.3)
  2. Check access control security level configuration
    Go to WordPress admin > miniOrange REST API > API Authentication > Access Control. Examine the 'Security Level' or 'Access Control' setting. Common options include 'Basic', 'Application Level', 'Limited', or custom configurations.
    Affected if Security level is set to a permissive or misconfigured option (for example, set to allow unauthenticated access or overly broad permissions)
  3. Verify REST API endpoint authorization
    Using a tool like curl or a browser developer console, send a GET request to a protected WordPress REST API endpoint (such as /wp-json/wp/v2/users or /wp-json/miniorange-api/v1/ ) without providing valid authentication headers. Inspect the response for successful data return versus a 401/403 error.
    Affected if The REST API returns sensitive data or allows access without requiring valid authentication (response shows 200 OK with data instead of 401/403 unauthorized)
  4. Review plugin settings for authorization enforcement
    Navigate to WordPress admin > miniOrange REST API > API Authentication > Configuration. Look for settings related to 'Authorization', 'Authentication', or 'API Key Validation' to confirm whether enforcement is properly enabled.
    Affected if Authorization enforcement is disabled, bypassed, or set to 'None'

The environment is affected if the miniOrange REST API Authentication plugin version is 3.6.3 or lower AND the access control security level is misconfigured to allow unauthorized access to REST API endpoints.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Review and correctly configure the plugin's access control security level settings, ensure proper authorization checks are enforced for all REST API endpoints, and update to the latest plugin version if available.

Recommended fix Moderate confidence

Latest available version (greater than 3.6.3)

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Find the miniOrange WordPress REST API Authentication plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin is running the most recent version in Plugins > Installed Plugins

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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