RegistrationmagicWordPress extension · Metagauss
CVE-2023-51509
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Metagauss RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login allows Reflected XSS.This issue affects RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login: from n/a through 5.2.4.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 · high confidenceA reflected XSS vulnerability exists in the RegistrationMagic WordPress plugin where user-supplied input in registration forms is not properly sanitized before being reflected back in the web page, allowing attackers to inject malicious JavaScript that executes in the context of the victim's browser.
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
<= 5.2.4.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify RegistrationMagic plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'RegistrationMagic' or 'Metagauss Registrationmagic' in the list. Check if the plugin is active.Affected if The plugin is installed and active
-
Identify the installed plugin versionIn the Plugins list, click on 'View details' or hover over the RegistrationMagic plugin entry to display the version number. Alternatively, check the plugin's main PHP file header in wp-content/plugins/registrationmagic/ for the Version field.Affected if Version is 5.2.4.1 or lower (any version up to and including 5.2.4.1)
-
Confirm registration forms existIn WordPress admin, navigate to RegistrationMagic > All Forms to list created registration forms. Check if any forms are published and active.Affected if Any published registration forms exist using this plugin
-
Determine if registration pages are publicly accessibleVisit the registration form URLs (typically under /?rm_login_form_id= or similar query parameters) to confirm they are accessible without admin authentication. Check if the pages accept user input in form fields.Affected if Registration form pages are publicly accessible and accept user-supplied input
You are affected if the installed RegistrationMagic plugin version is 5.2.4.1 or lower and you have active, publicly accessible registration forms that reflect user input back to the page.
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 to the latest version of RegistrationMagic plugin. Until patched, avoid clicking untrusted links to the affected registration pages and consider implementing additional web application firewall rules.
Fix this in Registrationmagic
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-51509 — 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-2023-51509 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