dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-32385

MEDIUM · 5.4 CVSS v3.1 Published 2026-03-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/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 Metagauss RegistrationMagic custom-registration-form-builder-with-submission-manager allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects RegistrationMagic: from n/a through <= 6.0.7.6.

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 vulnerability in the RegistrationMagic WordPress plugin (custom registration form builder with submission manager). The flaw allows attackers to exploit incorrectly configured access control security levels, enabling unauthorized access to certain functionality due to improper or missing authorization checks in the plugin.

MitigationUpdate RegistrationMagic to the latest patched version when available. Until then, implement additional access controls at the web application firewall or server level to restrict unauthorized access to the plugin's administrative functions.

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
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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. Confirm RegistrationMagic plugin is installed
    Navigate to WordPress admin > Plugins or inspect the wp-content/plugins/ directory for a folder named 'registration-magic' or similar
    Affected if The plugin folder exists and the plugin is active in WordPress
  2. Identify installed plugin version
    Check the main plugin file (e.g., registration-magic.php) for the 'Version' header, or view the plugin details in WordPress admin > Plugins
    Affected if The installed version is older than the patched version (compare against the latest version on the WordPress plugin repository)
  3. Enumerate user roles with access to plugin admin pages
    Log in as different user roles (subscriber, contributor, author, editor) and attempt to access RegistrationMagic admin pages directly via URL (e.g., /wp-admin/admin.php?page=registrationmagic'), or inspect role capabilities in the database
    Affected if Lower-privileged users (non-administrator) can access RegistrationMagic administrative functions without proper authorization
  4. Test for IDOR on plugin submission endpoints
    Using a low-privileged account, intercept requests when submitting forms or accessing submission data. Check if parameters like 'submission_id', 'form_id', or 'user_id' can be manipulated to access other users' data
    Affected if A user can view, modify, or delete submissions, forms, or user data belonging to other users without ownership or admin privileges
  5. Inspect plugin settings for security level misconfiguration
    In WordPress admin, go to RegistrationMagic > Settings > Security Settings (or similar). Check if 'Access Control' or 'User Levels' are set to allow low-privileged users to perform administrative actions
    Affected if Security level settings permit non-administrator users to access sensitive plugin features intended only for admins

The environment is affected if RegistrationMagic plugin is active and low-privileged users can access administrative functions or other users' data without proper 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 RegistrationMagic to the latest patched version when available. Until then, implement additional access controls at the web application firewall or server level to restrict unauthorized access to the plugin's administrative functions.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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