dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-58627

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Authorization Bypass Through User-Controlled Key vulnerability in kamleshyadav Miraculous Core Plugin miraculouscore allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Miraculous Core Plugin: from n/a through < 2.0.9.

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 Miraculous Core Plugin for WordPress contains an authorization bypass vulnerability where an attacker can manipulate a user-controlled key to bypass access control checks. This allows unauthorized access to protected functionality due to incorrectly configured security levels in the plugin's access control implementation.

MitigationUpgrade the Miraculous Core Plugin to version 2.0.9 or later. If immediate upgrade is not possible, review and harden access control logic around user-supplied keys and consider restricting administrative endpoints while awaiting the patch.

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
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. Identify the installed version of Miraculous Core Plugin
    Navigate to WordPress admin > Plugins > Installed Plugins > Miraculous Core, or check the main plugin file (usually miracl-core.php or similar) for the 'Version' header in the plugin metadata
    Affected if The installed version is lower than 2.0.9 or the version cannot be determined
  2. Locate access control configuration related to user-controlled keys
    Examine the plugin directory for files handling authentication or authorization logic (often in includes/, classes/, or core/ subdirectories). Search for code referencing 'key', 'access', 'authorize', or 'capability' parameters that accept user input
    Affected if The plugin contains custom access control code that relies on user-supplied key values for authorization decisions
  3. Verify the security level configuration for protected functionality
    Review the plugin's access control implementation to identify which functions or endpoints rely on user-controlled keys for permission validation. Check for roles/capabilities checks or whitelist logic
    Affected if Protected administrative functions or sensitive operations can be accessed by manipulating user-supplied key parameters without proper role verification
  4. Test whether unauthorized access is possible via key manipulation
    If you have access to the plugin's protected features, attempt to access them with modified or forged key parameter values to see if access control is enforced
    Affected if User-supplied keys can be manipulated to bypass the intended security level and access protected functionality without proper authorization

A user is affected if the Miraculous Core Plugin version is below 2.0.9 AND the plugin's access control logic uses user-controlled keys for authorization, allowing unauthorized access to protected features.

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

Upgrade the Miraculous Core Plugin to version 2.0.9 or later. If immediate upgrade is not possible, review and harden access control logic around user-supplied keys and consider restricting administrative endpoints while awaiting the patch.

Recommended fix Moderate confidence

2.0.9 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'Miraculous Core Plugin' (miraculouscore)
  4. Verify the currently installed version
  5. If the version is below 2.0.9, update the plugin to version 2.0.9 or later via the WordPress plugin update mechanism
  6. Alternatively, download version 2.0.9 or later from a trusted source and reinstall the plugin

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