dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-11204

HIGH · 7.2 CVSS v3.1 Published 2025-10-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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
The RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login plugin for WordPress is vulnerable to SQL Injection in all versions up to, and including, 6.0.6.2 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with administrator access or higher, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. An unauthenticated attacker could utilize an injected Cross-Site Scripting via user-agent on form submission to leverage this to achieve Reflected Cross-Site Scripting.

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 confidence

The RegistrationMagic WordPress plugin versions up to 6.0.6.2 contain a SQL Injection vulnerability due to insufficient escaping on user-supplied parameters combined with a lack of prepared statements in the existing SQL queries. Authenticated attackers with administrator-level privileges can inject malicious SQL queries to extract sensitive database information. An unauthenticated attack vector also exists via reflected XSS through the user-agent header during form submission.

MitigationUpdate the RegistrationMagic plugin to version 6.0.7 or later which contains the security patch. Until patched, restrict administrative access and implement WAF rules to block SQL injection patterns in requests.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify RegistrationMagic plugin is installed
    Check for the plugin directory at /wp-content/plugins/registrationmagic/ or search for 'registrationmagic.php' in the plugins folder. You can also list installed plugins via WP-CLI: wp plugin list --name=registrationmagic
    Affected if The plugin directory or files exist in the WordPress installation
  2. Determine the installed version
    Open the main plugin file (typically registrationmagic.php) and locate the version comment/header, or check the readme.txt file in the plugin directory. The version is often defined in a comment block at the top of the main PHP file
    Affected if The version number is 6.0.6.2 or lower (any version up to and including 6.0.6.2)
  3. Confirm admin user accounts exist
    In WordPress admin, go to Users > All Users and check for any user with Administrator role, or query the wp_usermeta table for meta_value='administrator'
    Affected if At least one administrator-level user account exists in the WordPress installation (required for the SQL injection attack vector)
  4. Check for publicly accessible forms
    Visit the site frontend and check if any RegistrationMagic forms are accessible without authentication. Forms are typically at URLs like /?regmagic_form=1 or /registration/, or check the form published status in the plugin admin panel
    Affected if RegistrationMagic forms are published and accessible to unauthenticated users (enables the reflected XSS via user-agent header)

You are affected if RegistrationMagic plugin version 6.0.6.2 or lower is installed AND (admin accounts exist for SQLi risk OR forms are publicly accessible for XSS risk).

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the RegistrationMagic plugin to version 6.0.7 or later which contains the security patch. Until patched, restrict administrative access and implement WAF rules to block SQL injection patterns in requests.

Recommended fix Moderate confidence

Version 6.0.6.3 or latest available version

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login'
  4. Click 'Update now' if an update is available, or manually upload the latest version from wordpress.org/plugins/registrationmagic
  5. After updating, verify the new version number is 6.0.6.3 or higher

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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