dbcve.org
CWE-288Weakness · CWE-288

CVE-2026-49764

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-15
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
Unauthenticated Broken Authentication in RegistrationMagic <= 6.0.8.6 versions.

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

Unauthenticated broken authentication vulnerability in the RegistrationMagic WordPress plugin affecting versions 6.0.8.6 and earlier. Attackers can bypass authentication mechanisms without credentials, gaining unauthorized access to the application.

MitigationUpgrade RegistrationMagic to the latest version immediately. If no patched version is available, disable the plugin until a fix is released.

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. Verify RegistrationMagic plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'RegistrationMagic' or check the plugin files in wp-content/plugins/registrationmagic/
    Affected if The plugin appears in the installed plugins list
  2. Identify the installed version number
    In WordPress admin, click on the RegistrationMagic plugin to view its details, or open the main plugin file (e.g., registrationmagic.php) and look for the 'Version' header in the plugin comment block
    Affected if Version number displayed is 6.0.8.6 or lower
  3. Confirm the plugin is active
    In WordPress admin > Plugins, verify the RegistrationMagic plugin shows as 'Active'
    Affected if Plugin status is Active (the vulnerability is unauthenticated, so it applies regardless of user login state)
  4. Check if user registration is enabled
    Go to RegistrationMagic settings > General Settings and look for user registration options, or check WordPress Settings > General > 'Membership' to see if 'Anyone can register' is checked
    Affected if User registration is enabled (this vulnerability allows bypassing auth, making registration capability relevant to exposure)

User is affected if RegistrationMagic plugin is installed, active, and the version is 6.0.8.6 or earlier, regardless of specific configuration since the flaw is an unauthenticated bypass.

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 RegistrationMagic to the latest version immediately. If no patched version is available, disable the plugin until a fix is released.

Recommended fix Moderate confidence

Upgrade RegistrationMagic to the latest available version (greater than 6.0.8.6)

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to WordPress Admin Dashboard > Plugins
  3. 3. Locate RegistrationMagic plugin in the installed plugins list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from the official WordPress plugin repository or RegistrationMagic's official website
  6. 6. After updating, verify the plugin version is greater than 6.0.8.6
  7. 7. Test user registration functionality to ensure the plugin continues to work correctly
  8. 8. Review user accounts for any unauthorized registrations that may have occurred during vulnerability exposure
Caveat Review plugin settings after upgrade as configuration changes may occur between versions

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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