dbcve.org
RegistrationmagicWordPress extension · Metagauss

CVE-2023-47645

HIGH · 8.8 CVSS v3.1 Published 2023-11-30
Fix available
A fix is available. Upgrade to 5.2.3.0 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in RegistrationMagic RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login allows Cross Site Request Forgery.This issue affects RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login: from n/a through 5.2.2.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

Cross-Site Request Forgery (CSRF) vulnerability in the RegistrationMagic WordPress plugin allows attackers to trick authenticated administrators into performing unintended actions (such as modifying registration forms, user data, or plugin settings) by exploiting the lack of anti-CSRF tokens on state-changing requests.

MitigationImplement anti-CSRF tokens (synchronizer token pattern) on all state-changing operations and validate Origin/Referer headers server-side; alternatively, update to the latest patched version of RegistrationMagic once available.

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.2.3.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Confirm RegistrationMagic plugin is installed
    Navigate to WordPress admin > Plugins and verify RegistrationMagic (Metagauss Registrationmagic) is listed as installed and active
    Affected if Plugin is installed and active on the WordPress site
  2. Check installed version number
    In the WordPress Plugins list, find RegistrationMagic and locate the version number displayed in the plugin description; alternatively, inspect the plugin header in the main PHP file
    Affected if Installed version is below 5.2.3.0
  3. Locate state-changing plugin pages
    Access the RegistrationMagic admin menu in WordPress dashboard and identify pages containing forms that modify registration forms, user data, or plugin settings
    Affected if State-changing forms exist in the plugin admin interface
  4. Inspect forms for anti-CSRF tokens
    View the HTML source of RegistrationMagic admin pages with forms; search for hidden input fields containing nonce values or CSRF tokens, or check if forms submit to endpoints that validate such tokens
    Affected if Forms lack anti-CSRF token fields or validation is missing

If RegistrationMagic version is below 5.2.3.0 and state-changing forms do not contain anti-CSRF token fields, the installation is affected by this vulnerability.

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.2.3.0 or later
Fixed in 5.2.3.0
Interim mitigation

Implement anti-CSRF tokens (synchronizer token pattern) on all state-changing operations and validate Origin/Referer headers server-side; alternatively, update to the latest patched version of RegistrationMagic once available.

Recommended fix High confidence

5.2.3.0

  1. 1. Create a complete backup of the WordPress site including database and files
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate RegistrationMagic (RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login) in the plugin list
  4. 4. Click the 'Update now' link if an update is available, or click 'Delete' and install version 5.2.3.0 fresh
  5. 5. Alternatively, download RegistrationMagic version 5.2.3.0 from the WordPress plugin repository or from the vendor
  6. 6. Upload and install the updated plugin via Plugins > Add New > Upload Plugin
  7. 7. After installation, verify the plugin version shows 5.2.3.0 or higher
  8. 8. Test that registration forms and related functionality work correctly

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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