dbcve.org
RegistrationmagicWordPress extension · Metagauss

CVE-2024-33947

MEDIUM · 6.1 CVSS v3.1 Published 2024-05-03
Fix available
A fix is available. Upgrade to 5.3.2.1 or later.
See remediation →
68/100
Remediation priority · Elevated
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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Metagauss RegistrationMagic allows Reflected XSS.This issue affects RegistrationMagic: from n/a through 5.3.2.0.

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

Reflected XSS vulnerability in RegistrationMagic plugin versions up to 5.3.2.0 allows attackers to inject malicious JavaScript through unsanitized user input that gets reflected in web pages without proper output encoding.

MitigationApply output encoding/escaping functions (such as esc_html, esc_attr in WordPress context) to all user-supplied input before rendering in HTML context. Update to latest plugin version if 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.3.2.1

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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
    Check if the /wp-content/plugins/registrationmagic directory exists, or list all installed plugins via WordPress admin or wp-cli plugin list
    Affected if Plugin directory or entry exists in the WordPress installation
  2. Determine installed plugin version
    Open the main plugin file (registrationmagic.php) and locate the 'Version' header in the plugin comment block, or check readme.txt for the version field
    Affected if Version is below 5.3.2.1 (e.g., 5.3.2.0 or earlier)
  3. Confirm plugin is active
    Check WordPress admin Plugins page or run: wp plugin status registrationmagic
    Affected if Plugin shows as 'Active' or 'Enabled'
  4. Identify registration form pages
    Navigate to RegistrationMagic settings in WordPress admin and list all active registration forms. Look for pages or shortcodes where user input is collected
    Affected if One or more registration forms exist and are published
  5. Check for user input reflection
    Submit test input (e.g., <script>alert(1)</script>) through a registration form and inspect the resulting page source to see if the input is reflected without encoding
    Affected if User-supplied data appears in HTML output without escaping (visible as raw script tags in page source)

If RegistrationMagic is installed, active, and running version 5.3.2.0 or below, the environment is vulnerable to reflected XSS via unsanitized user input in registration forms.

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.3.2.1 or later
Fixed in 5.3.2.1
Interim mitigation

Apply output encoding/escaping functions (such as esc_html, esc_attr in WordPress context) to all user-supplied input before rendering in HTML context. Update to latest plugin version if available.

Recommended fix Moderate confidence

5.3.2.1

  1. 1. Backup your WordPress site and database before performing any updates.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Locate the RegistrationMagic plugin in the list.
  4. 4. If an update is available, click 'Update Now' to update to the latest version.
  5. 5. Alternatively, you can download version 5.3.2.1 from the official WordPress plugin repository or Metagauss website and manually upload it via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the plugin is running version 5.3.2.1 or higher.
  7. 7. Test the registration forms to ensure functionality remains intact.

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

Fix this in Registrationmagic Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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