CVE-2026-24374
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Metagauss RegistrationMagic custom-registration-form-builder-with-submission-manager allows Cross Site Request Forgery.This issue affects RegistrationMagic: from n/a through <= 6.0.6.9.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in RegistrationMagic WordPress plugin allows attackers to forge requests on behalf of authenticated administrators. The plugin lacks proper anti-CSRF token validation on state-changing operations, enabling unauthorized form submissions and configuration changes.
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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm RegistrationMagic plugin installationIn WordPress admin, go to Plugins > Installed Plugins and look for 'RegistrationMagic' or 'RegistrationMagic - Custom Registration Forms' entry; alternatively, check wp-content/plugins/ directory for registration-magic folderAffected if Plugin is installed and active
-
Identify installed plugin versionIn WordPress admin_plugins list, find RegistrationMagic and read the version number from the plugin row; or open registration-magic/readme.txt and check the Version headerAffected if Version is earlier than the patched release containing CSRF fix
-
Check for nonce validation in plugin formsUsing a code search tool, scan plugin PHP files for presence of wp_verify_nonce, check_admin_referer, or wp_create_nonce in form handling code, especially files in the handlers, admin, or includes foldersAffected if State-changing form handlers lack nonce verification functions
-
Inspect AJAX handlers for CSRF protectionSearch plugin files for add_action calls with wp_ajax_ and verify if the callback functions call wp_verify_nonce or check_admin_referer before processingAffected if AJAX endpoints performing database writes or settings changes do not validate nonces
-
Verify admin action hooks for nonce checksExamine plugin files for admin_action hooks or admin_post handlers and confirm they validate request nonces before executing state-changing operationsAffected if Admin post handlers skip nonce validation before modifying settings or user data
Environment is affected if RegistrationMagic plugin is installed without the CSRF fix and the plugin code does not implement nonce validation on its state-changing operations.
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 dataImplement WordPress nonces (wp_verify_nonce/check_admin_referer) on all forms and AJAX handlers performing state-changing operations; add SameSite cookie attributes; verify request origin headers.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24374 — 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-24374 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