dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-1865

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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 User Registration & Membership – Free & Paid Memberships, Subscriptions, Content Restriction, User Profile, Custom User Registration & Login Builder plugin for WordPress is vulnerable to SQL Injection via the ‘membership_ids[]’ parameter in all versions up to, and including, 5.1.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 Subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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

SQL Injection vulnerability in the User Registration & Membership WordPress plugin allows authenticated attackers with Subscriber-level access to inject malicious SQL queries via the unsanitized 'membership_ids[]' parameter due to insufficient input escaping and lack of prepared statements in the existing SQL query.

MitigationUpdate the plugin to version 5.1.3 or later. As a defense-in-depth measure, review and restrict the capabilities assigned to Subscriber-level users.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 the User Registration & Membership plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'User Registration & Membership' or check the wp-content/plugins directory for a folder named similarly
    Affected if The plugin is present in the WordPress installation
  2. Check the installed plugin version
    In Plugins > Installed Plugins, click on the plugin to view its version details, or inspect the plugin's main PHP file for a 'Version:' header in the plugin comment block
    Affected if The version is any version prior to the patched release (compare against the vendor's current version)
  3. Confirm the membership_ids parameter is in use
    Search the plugin files for 'membership_ids' or 'membership_ids[]' to locate the vulnerable code path; typical locations include AJAX handlers or form processing files
    Affected if The parameter handling code exists and processes user input without prepared statements
  4. Verify subscriber-level accounts exist
    In WordPress admin, go to Users and review roles assigned; check for any user with the Subscriber role
    Affected if At least one user with Subscriber role or higher can access the vulnerable endpoint
  5. Check if the vulnerable endpoint is accessible
    Identify the AJAX action or form submission that handles membership_ids (often found in plugin's admin-ajax.php calls or front-end forms); attempt to access it with a test subscriber account if possible
    Affected if The endpoint processes membership_ids[] without sanitization using $wpdb->prepare() or equivalent prepared statements

A user is affected if the plugin is installed, the vulnerable parameter handling exists, and an authenticated user with Subscriber-level access can reach the SQL query endpoint.

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 plugin to version 5.1.3 or later. As a defense-in-depth measure, review and restrict the capabilities assigned to Subscriber-level users.

Recommended fix Moderate confidence

5.1.3 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the 'User Registration & Membership' plugin
  4. 4. Check if an update to version 5.1.3 or higher is available
  5. 5. If available, update the plugin to the latest version
  6. 6. Verify the update was successful by checking the plugin version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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