dbcve.org
ArmemberWordPress extension · Armemberplugin

CVE-2022-42888

HIGH · 8.8 CVSS v3.1 Published 2022-12-06
Fix available
A fix is available. Upgrade to after 5.5.1 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Unauth. Privilege Escalation vulnerability in ARMember premium plugin <= 5.5.1 on WordPress.

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

This is an unauthenticated privilege escalation vulnerability in the ARMember premium WordPress plugin versions 5.5.1 and below. An attacker without valid credentials can elevate their privileges to administrator-level access, potentially taking full control of the WordPress site.

MitigationUpdate ARMember premium plugin to a version newer than 5.5.1. If immediate update is not possible, consider restricting access to the plugin or implementing additional authentication layers.

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:<= 5.5.1

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Locate ARMember plugin installation
    Check the WordPress plugins directory (wp-content/plugins/armember) or view installed plugins in WordPress admin under Plugins > Installed Plugins. Look for 'ARMember' or 'Armemberplugin' entry.
    Affected if ARMember premium plugin is found installed on the WordPress site
  2. Identify installed version
    In WordPress admin, click on the ARMember plugin to view its details, or inspect the main plugin file (usually armember.php) and look for a version comment/constant at the top of the file.
    Affected if The displayed version number is 5.5.1 or lower (any version <= 5.5.1)
  3. Verify unauthenticated access is possible
    Check the site configuration to confirm the ARMember REST API or registration endpoints are publicly accessible without authentication. Look for WordPress API access settings in ARMember > General Settings > Access Settings.
    Affected if Registration or membership API endpoints are exposed to unauthenticated users (no login required to access them)
  4. Audit administrator accounts
    Navigate to WordPress Users > All Users and review all accounts with Administrator role. Look for unfamiliar accounts created recently or accounts that were not created through standard WordPress admin processes.
    Affected if There are unexpected administrator accounts present, especially ones created around the time the vulnerability became known or recently

If the ARMember premium plugin version 5.5.1 or lower is installed and its membership/registration features are publicly accessible, the site is likely affected by this privilege escalation vulnerability.

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 a release after 5.5.1
Interim mitigation

Update ARMember premium plugin to a version newer than 5.5.1. If immediate update is not possible, consider restricting access to the plugin or implementing additional authentication layers.

Recommended fix Moderate confidence

ARMember premium plugin version 5.5.2 or latest available version

  1. 1. Check current installed version of ARMember plugin in WordPress admin under Plugins section
  2. 2. Navigate to Plugins > Add New > Upload or access your WordPress plugin repository to obtain the latest version
  3. 3. Before updating, backup your WordPress database and files
  4. 4. Update ARMember plugin to the latest version available from the official WordPress plugin repository or ARMember vendor
  5. 5. Verify the update was successful and test user registration and privilege functionality
  6. 6. Check ARMember's official release notes or changelog for version 5.5.2 or later for security fixes
Caveat Review plugin changelog for potential compatibility issues with other plugins or customizations before upgrading

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

Fix this in Armember Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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