CVE-2025-49388
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 · uneditedIncorrect Privilege Assignment vulnerability in kamleshyadav Miraculous Core Plugin miraculouscore allows Privilege Escalation.This issue affects Miraculous Core Plugin: from n/a through <= 2.0.7.
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 confidenceThe Miraculous Core Plugin for WordPress contains an Incorrect Privilege Assignment vulnerability (CWE-266) that allows authenticated users to escalate their privileges beyond what their assigned role should permit, potentially gaining administrative access. The CVSS 9.8 indicates this is exploitable over the network with no privileges required.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Miraculous Core Plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins, or inspect /wp-content/plugins/ directory for a folder containing 'miraculous' or 'miraculous-core'.Affected if The Miraculous Core Plugin folder exists in the WordPress plugins directory.
-
Identify installed plugin versionIn WordPress admin, click 'View Details' on the Miraculous Core Plugin to display the version number. Alternatively, check the plugin's main PHP file for the 'Version' header in the plugin comment block.Affected if The displayed version matches or precedes the last known vulnerable version (compare against official WordPress plugin repository release notes).
-
Audit user accounts for privilege escalationGo to WordPress admin > Users > All Users and review all accounts. Check for unfamiliar administrators, accounts with administrator role that were created recently, or accounts with elevated capabilities not matching their expected role.Affected if There are administrator accounts that were created without explicit admin action, or user role modifications occurred that were not initiated by an administrator.
-
Inspect plugin role modification capabilitiesExamine the plugin's source files (especially in includes/ or classes/ subdirectories) for functions that modify user roles, capabilities, or metadata. Look for endpoints that accept user IDs and role parameters without proper capability checks.Affected if The plugin contains code that assigns or modifies user roles/capabilities without verifying the requesting user has administrative privileges.
A user is affected if the Miraculous Core Plugin is installed and either the version is unpatched or unauthorized administrator accounts exist in the WordPress user database.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate to a patched version of the Miraculous Core Plugin immediately; if no patched version is available, disable the plugin until a fix can be applied. Audit user accounts for unauthorized privilege changes.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49388 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-49388 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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