dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-2363

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-04
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 WP-Members Membership Plugin plugin for WordPress is vulnerable to SQL Injection via the 'order_by' attribute of the [wpmem_user_membership_posts] shortcode in all versions up to, and including, 3.5.5.1. This is 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 Contributor-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

The WP-Members Membership Plugin for WordPress is vulnerable to SQL Injection via the 'order_by' parameter of the [wpmem_user_membership_posts] shortcode. The parameter is not properly escaped before use in an SQL query, and the existing query lacks prepared statements, allowing authenticated attackers with Contributor-level access to inject arbitrary SQL and extract sensitive data.

MitigationUpdate the plugin to a version beyond 3.5.5.1 when available, or implement proper input sanitization and prepared statements for the 'order_by' parameter in the shortcode handler.

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. Check if WP-Members plugin is installed and identify its version
    Navigate to WordPress admin > Plugins > Installed Plugins. Locate 'WP-Members Membership' and note the version number displayed. Alternatively, access via FTP/file manager and check the main plugin file (usually wp-members/wp-members.php) for the 'Version' header in the plugin comments.
    Affected if The plugin is installed and the version is 3.5.5.1 or lower.
  2. Locate uses of the vulnerable shortcode
    Search your WordPress content (posts, pages, custom post types) for the string '[wpmem_user_membership_posts]'. Use WordPress search, or query the wp_posts table directly: SELECT ID, post_title, post_type FROM wp_posts WHERE post_content LIKE '%wpmem_user_membership_posts%' AND post_status = 'publish';
    Affected if The shortcode [wpmem_user_membership_posts] is present in any published content.
  3. Verify if the order_by parameter is used in the shortcode
    Examine the shortcode usage found in Step 2. Look for the 'order_by' attribute within the shortcode tag, for example: [wpmem_user_membership_posts order_by='...']. If using a page builder or custom post type, inspect the stored content directly in the database.
    Affected if The shortcode includes an 'order_by' parameter, which enables the vulnerable code path.
  4. Confirm user role access on the site
    Review which user roles exist on the WordPress site. Navigate to Users > All Users and note the roles assigned. The vulnerability is exploitable by users with Contributor-level access or higher.
    Affected if Any user account with Contributor, Author, Editor, or Administrator role exists on the site.

You are affected if the WP-Members plugin version is 3.5.5.1 or lower AND the [wpmem_user_membership_posts] shortcode with an 'order_by' parameter is in use on your site, allowing any authenticated user with Contributor-level access to exploit the SQL Injection.

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 a version beyond 3.5.5.1 when available, or implement proper input sanitization and prepared statements for the 'order_by' parameter in the shortcode handler.

Recommended fix Moderate confidence

Upgrade to WP-Members Membership Plugin version 3.5.6 or latest available version

  1. 1. Log in to the WordPress admin dashboard with an administrator account
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the WP-Members Membership Plugin in the plugin list
  4. 4. If an update is available, click 'Update Now' to update to the latest version (3.5.6 or higher)
  5. 5. Alternatively, download the latest version from the WordPress Plugin Repository at https://wordpress.org/plugins/wp-members/
  6. 6. Deactivate and delete the current plugin, then upload and activate the new version
  7. 7. Verify the update was successful by checking the plugin version in the Plugins list

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 / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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