CVE-2026-7649
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 · uneditedThe ARMember – Membership Plugin, Content Restriction, Member Levels, User Profile & User signup plugin for WordPress is vulnerable to time-based blind SQL Injection via the 'orderby' parameter in all versions up to, and including, 4.0.60 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. 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 confidenceThe ARMember WordPress plugin versions up to 4.0.60 contain a time-based blind SQL Injection vulnerability in the 'orderby' parameter. The flaw results from insufficient escaping of user-supplied input combined with lack of prepared statements in the underlying SQL query, allowing unauthenticated attackers to inject arbitrary SQL commands.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify ARMember plugin is installedLog in to WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for ARMember in the list. Alternatively, check the wp-content/plugins/armember directory exists on the server.Affected if ARMember plugin is present and active on the WordPress site
-
Determine installed ARMember versionIn WordPress admin, go to Plugins > Installed Plugins > ARMember and view the version number displayed. Or check the main plugin file (e.g., armember.php) for the 'Version' header comment.Affected if The installed version is 4.0.60 or lower (any version up to and including 4.0.60)
-
Confirm vulnerable endpoint is accessibleIdentify if the site uses ARMember's frontend listing or membership pages that accept an 'orderby' parameter via GET or POST request. Common paths include pages with shortcodes like [arm_member_listing] or similar. Test accessing a page with '?orderby=id' appended to the URL.Affected if The site exposes pages that process the 'orderby' parameter without authentication requirement
-
Review request logs for SQL injection attemptsExamine web server access logs (Apache/nginx) or WAF logs for requests to ARMember pages containing suspicious 'orderby' values such as 'orderby=sleep(X)' or other time-based SQL functions.Affected if Log analysis reveals unauthenticated requests with SQL injection payloads in the 'orderby' parameter
A site is affected if it runs ARMember version 4.0.60 or lower AND has frontend pages that accept the 'orderby' parameter without proper authentication, exposing the SQL injection vulnerability to unauthenticated attackers.
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 the ARMember plugin to a version newer than 4.0.60, which should contain proper input sanitization and prepared statements for the 'orderby' parameter.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7649 — 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-2026-7649 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