dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-32516

HIGH · 8.5 CVSS v3.1 Published 2026-03-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in kamleshyadav Miraculous Core Plugin miraculouscore allows Blind SQL Injection.This issue affects Miraculous Core Plugin: from n/a through < 2.1.2.

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 · high confidence

A blind SQL injection vulnerability exists in the Miraculous Core Plugin (miraculouscore) for WordPress. The vulnerability allows unauthenticated attackers to inject malicious SQL queries through unsanitized user input, potentially enabling data exfiltration from the database. The issue affects all versions prior to 2.1.2.

MitigationUpgrade to Miraculous Core Plugin version 2.1.2 or later. If patching is not immediately possible, disable the plugin until an update can be applied. The fix requires reviewing all database query paths and implementing prepared statements or proper input sanitization.

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
Changed
Confidentiality
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/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. Check if Miraculous Core Plugin is installed
    Navigate to WordPress admin > Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'miraculouscore'
    Affected if The plugin folder 'miraculouscore' exists in the plugins directory
  2. Determine the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Miraculous Core, and read the version number displayed under the plugin name. Alternatively, open the main plugin file (e.g., /wp-content/plugins/miraculouscore/miraculouscore.php) and locate the 'Version' header in the plugin metadata comment block
    Affected if The displayed version number is lower than 2.1.2 (for example: 2.1.1, 2.0.5, 1.x.x, or no version is shown)
  3. Verify the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and check if Miraculous Core shows an 'Active' status under the plugin name
    Affected if The plugin shows as 'Active' and the version is below 2.1.2
  4. Confirm the vulnerability is exploitable
    Since this is an unauthenticated blind SQL injection via unsanitized user input, confirm that the plugin is exposed to public-facing pages or API endpoints. Check for publicly accessible URLs that may invoke the plugin (e.g., front-end ajax endpoints, shortcodes, or widget areas where the plugin renders content)
    Affected if The plugin is active and publicly accessible without requiring authentication, and the version is below 2.1.2

The environment is affected if the Miraculous Core Plugin is installed, active, and running a version lower than 2.1.2.

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 to Miraculous Core Plugin version 2.1.2 or later. If patching is not immediately possible, disable the plugin until an update can be applied. The fix requires reviewing all database query paths and implementing prepared statements or proper input sanitization.

Recommended fix Moderate confidence

2.1.2

  1. Access the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Miraculous Core Plugin' (miraculouscore) by kamleshyadav
  4. Check if the current version is below 2.1.2
  5. If an update is available, click 'Update Now' to upgrade to version 2.1.2 or later
  6. Alternatively, download version 2.1.2 or latest from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  7. After updating, verify the plugin is running version 2.1.2 or higher under 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
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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