dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-5073

HIGH · 7.5 CVSS v3.1 Published 2026-06-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 ARMember Premium plugin for WordPress is vulnerable to SQL Injection via the 'order' parameter of the 'arm_directory_paging_action' AJAX action in all versions up to, and including, 7.3.1. This is due to insufficient escaping on the user-supplied 'order' and 'orderby' parameters and the lack of sufficient preparation on the existing SQL query in the `arm_get_directory_members()` function. This makes it possible for unauthenticated attackers 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 ARMember Premium WordPress plugin up to version 7.3.1 contains an unauthenticated SQL injection vulnerability in the arm_directory_paging_action AJAX handler. The 'order' and 'orderby' parameters are not properly escaped before being used in the arm_get_directory_members() function's SQL query, allowing attackers to inject arbitrary SQL commands.

MitigationUpdate the ARMember Premium plugin to a version newer than 7.3.1. If no update is available, implement input validation and use $wpdb->prepare() for the order/orderby parameters in the arm_get_directory_members() function.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 ARMember Premium plugin is installed
    Check for the plugin directory at wp-content/plugins/armember-membership/ or query the WordPress database: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins' OR query plugin files for version header in main plugin file
    Affected if ARMember Premium plugin directory exists or is listed in active plugins
  2. Determine installed ARMember Premium version
    Read the version from the plugin main file header (e.g., armember-membership.php) or query: SELECT meta_value FROM wp_postmeta WHERE meta_key = 'plugin_version'
    Affected if Version is 7.3.1 or lower (any version up to and including 7.3.1)
  3. Confirm arm_directory_paging_action AJAX handler exists
    Search plugin files for 'arm_directory_paging_action' in PHP files, or attempt authenticated check: grep -r 'arm_directory_paging_action' wp-content/plugins/armember-membership/
    Affected if The AJAX action handler is present in the plugin code
  4. Check arm_get_directory_members function for prepared statements
    Locate the arm_get_directory_members() function in plugin files and inspect how $order and $orderby parameters are used in SQL queries: grep -A 20 'function arm_get_directory_members' wp-content/plugins/armember-membership/*.php
    Affected if The function uses $order or $orderby variables directly in SQL without $wpdb->prepare() or input sanitization

Environment is affected if ARMember Premium plugin version is 7.3.1 or lower AND the arm_directory_paging_action handler exists with unparameterized order/orderby usage in arm_get_directory_members().

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 ARMember Premium plugin to a version newer than 7.3.1. If no update is available, implement input validation and use $wpdb->prepare() for the order/orderby parameters in the arm_get_directory_members() function.

Recommended fix Moderate confidence

ARMember Premium version 7.3.2 or later

  1. Check the WordPress admin dashboard for ARMember Premium plugin updates
  2. Navigate to Plugins > All Plugins > ARMember Premium
  3. If an update is available, update to the latest version (version 7.3.2 or later)
  4. Alternatively, download the latest version from the CodeCanyon marketplace or the developer's website
  5. After updating, verify the patch was applied by checking the arm_get_directory_members() function for proper SQL preparation
Caveat Review plugin settings after upgrade as minor configuration adjustments may be needed

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-5073 — 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-5073 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