dbcve.org
RegistrationmagicWordPress extension · Metagauss

CVE-2023-23976

HIGH · 7.5 CVSS v3.1 Published 2024-04-24
Fix available
A fix is available. Upgrade to 5.1.9.3 or later.
See remediation →
84/100
Remediation priority · High
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
Incorrect Default Permissions vulnerability in Metagauss RegistrationMagic allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects RegistrationMagic: from n/a through 5.1.9.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 · moderate confidence

RegistrationMagic plugin for WordPress versions through 5.1.9.2 contains incorrect default permissions that allow unauthorized users to access functionality not properly constrained by ACLs. This access control vulnerability enables attackers to potentially reach administrative or privileged functions without proper authorization.

MitigationUpdate RegistrationMagic to the latest patched version. Review user role and capability configurations in the plugin settings to ensure all sensitive functions are properly protected by ACLs.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RegistrationmagicWordPress extension
Affected:< 5.1.9.3

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

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
    Navigate to WordPress admin dashboard > Plugins and look for 'RegistrationMagic' or 'Metagauss Registrationmagic' in the installed plugins list
    Affected if RegistrationMagic plugin appears in the plugins list and is activated
  2. Check installed plugin version
    Click on the plugin name in the plugins list to view its details, or inspect the main plugin file header in wp-content/plugins/registration-magic/registration-magic.php for the 'Version' field
    Affected if The version number displayed is below 5.1.9.3 (e.g., 5.1.9.2, 5.1.9.1, etc.)
  3. Identify accessible plugin functionality
    Review the plugin settings pages under the RegistrationMagic menu item in the admin dashboard. Look for any public-facing forms, AJAX endpoints, or API routes that the plugin exposes
    Affected if The plugin exposes any administrative functions, form submissions, or data export features that do not require authentication or specific user capabilities
  4. Test for unauthorized ACL access
    Attempt to access RegistrationMagic admin functions using a WordPress user account with Subscriber or Contributor role (the lowest privilege roles). Try accessing direct URLs to plugin pages such as registration-magic/admin and any ajax endpoints
    Affected if A low-privilege user can access pages, modify settings, view submissions, or execute functions that should be restricted to Administrators only

A user is affected if RegistrationMagic plugin version is below 5.1.9.3 and the plugin exposes administrative functions to unauthorized or low-privilege users due to missing ACL constraints.

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
Upgrade available Upgrade to 5.1.9.3 or later
Fixed in 5.1.9.3
Interim mitigation

Update RegistrationMagic to the latest patched version. Review user role and capability configurations in the plugin settings to ensure all sensitive functions are properly protected by ACLs.

Recommended fix High confidence

5.1.9.3

  1. 1. Backup your WordPress database and files before making any changes
  2. 2. Navigate to WordPress Admin Dashboard > Plugins > Installed Plugins
  3. 3. Find RegistrationMagic in the plugin list
  4. 4. Click 'Update Now' if an update is available, or manually upload version 5.1.9.3
  5. 5. After updating, verify the plugin version shows 5.1.9.3
  6. 6. Test that registration forms and related functionality work correctly
  7. 7. Verify that file permissions on the plugin directory are set correctly (directories should be 755, files should be 644)
Caveat Review plugin settings after upgrade as minor configuration changes may occur

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

Fix this in Registrationmagic Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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