dbcve.org
ArmemberWordPress extension · Reputeinfosystems

CVE-2022-46808

CRITICAL · 9.8 CVSS v3.1 Published 2023-11-03
Fix available
A fix is available. Upgrade to 4.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Repute Infosystems ARMember armember-membership allows SQL Injection.This issue affects ARMember: from n/a through 3.4.11.

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 · moderate confidence

SQL Injection vulnerability in ARMember WordPress plugin allows attackers to inject malicious SQL commands through unsanitized user input. The vulnerability exists in the armember-membership component and could enable unauthorized database access, data exfiltration, or modification.

MitigationUpgrade ARMember to a version beyond 3.4.11 that contains the security patch. As a temporary measure, implement web application firewall rules and review plugin code for unsanitized database queries using prepared statements.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ArmemberWordPress extension
Affected:< 4.0

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm ARMember plugin installation
    Navigate to WordPress admin dashboard under Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'armember' or similar
    Affected if ARMember plugin is present on the WordPress site
  2. Identify installed ARMember version
    In WordPress admin, view the plugin details to read the version number, or open the main plugin file (e.g., armember.php) and locate the version constant or header
    Affected if The reported version is below 4.0 (versions 3.4.11 and earlier are specifically known to be vulnerable)
  3. Verify armember-membership component is active
    Check WordPress plugin settings or inspect the /wp-content/plugins/armember/ directory for an armember-membership folder or module; examine if the membership component is enabled in plugin configuration
    Affected if The armember-membership component is installed and active on the site
  4. Locate user input fields interacting with the membership component
    Inspect forms or frontend pages that use ARMember membership functionality (e.g., registration, login, profile forms); review the armember-membership PHP files for direct $_POST, $_GET, or $_REQUEST usage in database queries
    Affected if User-supplied input from form fields is being used in SQL queries without prepared statements or sanitization within the armember-membership code

The environment is affected if ARMember version is below 4.0 and the armember-membership component processes unsanitized user input in database queries.

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
Upgrade available Upgrade to 4.0 or later
Fixed in 4.0
Interim mitigation

Upgrade ARMember to a version beyond 3.4.11 that contains the security patch. As a temporary measure, implement web application firewall rules and review plugin code for unsanitized database queries using prepared statements.

Recommended fix Moderate confidence

ARMember version 4.0 or later

  1. 1. Back up your WordPress site and database before performing any upgrade.
  2. 2. Download ARMember version 4.0 or later from the official source (WordPress repository or ARMember website).
  3. 3. Deactivate the current ARMember plugin through WordPress admin dashboard.
  4. 4. Replace the existing ARMember files with the new version 4.0+ files.
  5. 5. Reactivate the ARMember plugin.
  6. 6. Verify that membership functionality continues to work correctly.
  7. 7. Test that the SQL injection vulnerability is no longer present by reviewing server logs for suspicious SQL patterns.
Caveat Review the ARMember changelog for version 4.0 to check for any breaking changes in functionality or template modifications

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

Fix this in Armember Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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