dbcve.org
ArmemberWordPress extension · Reputeinfosystems

CVE-2022-47425

HIGH · 8.8 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 3.4.11 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
Missing Authorization vulnerability in Repute Infosystems ARMember allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects ARMember: from n/a through 3.4.10.

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

ARMember WordPress plugin versions up to 3.4.10 contain a missing authorization vulnerability that allows attackers to exploit incorrectly configured access control security levels. This likely enables authenticated users to bypass intended membership tier restrictions or access privileged functionality beyond their authorized role, given the CVSS 8.8 score indicates significant impact.

MitigationImplement proper capability checks and role-based access control (RBAC) validation at all sensitive endpoints within ARMember, and ensure membership level verification cannot be bypassed through parameter tampering or direct object reference.

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:< 3.4.11

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. Check ARMember plugin version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins > ARMember, or inspect the plugin header in /wp-content/plugins/armember/ directory to find the version number
    Affected if Version is below 3.4.11 (e.g., 3.4.10, 3.4.9, etc.)
  2. Verify access control security level configuration
    Go to ARMember settings > Security/Access Control section in WordPress admin panel and review the permission tiers assigned to user roles for privileged functions
    Affected if Lower-tier user roles (e.g., Subscriber, Free Member) are granted access to functions restricted to higher permission tiers like Administrator or specific privilege levels
  3. Inspect user role capability assignments
    Navigate to ARMember > Members > User Roles or Access Rules and examine which capabilities are assigned to each membership level or user role
    Affected if Users with basic/free membership levels have permissions typically reserved for admin or premium tiers
  4. Test for unauthorized access to privileged functions
    Using a low-privilege user account (e.g., free/subscriber level), attempt to access admin functions or membership management features that should require higher authorization
    Affected if Low-privilege users can successfully access or modify settings/functions meant only for administrators or higher security levels

Affected if running ARMember version lower than 3.4.11 AND having access control security levels misconfigured to grant lower-tier users access to privileged functions

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 3.4.11 or later
Fixed in 3.4.11
Interim mitigation

Implement proper capability checks and role-based access control (RBAC) validation at all sensitive endpoints within ARMember, and ensure membership level verification cannot be bypassed through parameter tampering or direct object reference.

Recommended fix High confidence

ARMember version 3.4.11 or later

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to the WordPress admin dashboard > Plugins > Installed Plugins
  3. 3. Locate ARMember in the plugin list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 3.4.11 or later
  5. 5. Alternatively, download ARMember version 3.4.11 from the official WordPress plugin repository or the vendor website
  6. 6. Deactivate the current ARMember plugin, then upload and install the updated version
  7. 7. After updating, clear any caching mechanisms and verify the plugin is active
  8. 8. Test that member access controls and authorization settings are functioning correctly

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

Fix this in Armember Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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