CVE-2026-24373
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 Metagauss RegistrationMagic custom-registration-form-builder-with-submission-manager allows Privilege Escalation.This issue affects RegistrationMagic: from n/a through <= 6.0.7.1.
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 confidenceRegistrationMagic WordPress plugin versions up to 6.0.7.1 contains an incorrect privilege assignment vulnerability that allows authenticated users to escalate their privileges beyond what they should have access to, potentially achieving administrative or higher-level access they are not authorized for.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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.
-
Locate RegistrationMagic plugin installationCheck the WordPress plugins directory (wp-content/plugins) for a folder named 'registrationmagic' or 'registration-magic'. Use command: ls wp-content/plugins/ | grep -i registrationAffected if The plugin folder exists in the WordPress installation
-
Identify installed plugin versionRead the plugin header from the main PHP file (typically registrationmagic.php or similar in the plugin folder) to find the 'Version' field. Alternatively, check in WordPress admin under Plugins > Installed Plugins.Affected if Version is 6.0.7.1 or lower (any version up to and including 6.0.7.1)
-
Verify authenticated user access existsCheck WordPress user roles and capabilities database table (wp_users and wp_usermeta) for non-administrator user accounts. Look for users with roles other than Administrator.Affected if There are authenticated users with any role level (subscriber, contributor, author, editor) present in the system
-
Confirm privilege assignment functionality is in useReview the RegistrationMagic plugin settings in WordPress admin panel under the plugin's user role or capability configuration pages. Check if role/custom capability assignment features are enabled.Affected if The plugin's role management or capability assignment features are active or configured
You are affected if RegistrationMagic plugin is installed with version 6.0.7.1 or lower AND your site has authenticated non-administrative user accounts with the plugin's privilege assignment features in use.
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 RegistrationMagic plugin to the latest version beyond 6.0.7.1 to obtain the security patch that corrects the privilege assignment logic.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24373 — 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-2026-24373 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