dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-54745

MEDIUM · 6.5 CVSS v3.1 Published 2025-12-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/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 miniOrange's Google Authenticator miniorange-2-factor-authentication allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects miniOrange's Google Authenticator: from n/a through <= 6.1.1.

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

This is a missing authorization (authorization bypass) vulnerability in miniOrange's 2-factor authentication WordPress plugin. The flaw allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized access to protected functionality or resources that should require proper authentication and authorization checks.

MitigationUpdate to the latest version of the miniOrange 2-factor authentication plugin that addresses the missing authorization checks, or review and remediate the access control security level configuration.

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
High
Availability
None

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

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 2FA plugin is installed
    Navigate to WordPress admin dashboard > Plugins section and look for 'miniOrange 2-Factor Authentication' or search for it in the installed plugins list
    Affected if The miniOrange 2-Factor Authentication plugin appears in the list of installed plugins
  2. Determine the installed plugin version
    In the Plugins list, click on the miniOrange 2FA plugin details link or hover over the plugin name to reveal the version number. Alternatively, open the main plugin file (usually in wp-content/plugins/miniorange-2-factor-authentication/) and look for the 'Version' header in the plugin metadata
    Affected if The displayed version number matches or predates any version that contains the authorization fix (when no specific version is available, assume versions prior to the latest release may be affected)
  3. Review access control security level configuration
    Go to the miniOrange 2FA plugin settings page in WordPress admin (usually under 'miniOrange 2-Factor' or 'Security' menu). Look for security level, access control, or authentication policy settings. Check if the 'Security Level' or 'Access Control' is set to a configuration that permits unauthenticated or improperly authenticated access
    Affected if The security level is set to a value that does not require proper authentication and authorization for accessing protected plugin features, or is configured to allow public/unauthenticated access to admin functions
  4. Audit admin user roles and permissions
    Navigate to WordPress Users > All Users and verify which user roles have access to the miniOrange 2FA plugin settings. Check if any role without administrative privileges has been granted access to protected plugin functionality
    Affected if Non-administrator users or roles have been granted access to plugin features or settings that should require administrator-level authorization

The environment is affected if the miniOrange 2-Factor Authentication plugin is installed with a security level configuration that allows unauthenticated or improperly authorized access to protected functionality, or if the plugin version predates the fix for missing authorization checks.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of the miniOrange 2-factor authentication plugin that addresses the missing authorization checks, or review and remediate the access control security level configuration.

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-54745 — 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-54745 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