dbcve.org
ArmemberWordPress extension · Reputeinfosystems

CVE-2022-47424

HIGH · 8.8 CVSS v3.1 Published 2024-11-19
Fix available
A fix is available. Upgrade to 4.0.6 / 6.7.1 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Repute InfoSystems ARMember, Repute InfoSystems ARMember Premium allows Cross-Site Request Forgery.This issue affects ARMember: from n/a through 4.0.5; ARMember Premium: from n/a before 6.7.1.

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

Cross-Site Request Forgery (CSRF) vulnerability in Repute InfoSystems ARMember (through 4.0.5) and ARMember Premium (before 6.7.1) allows authenticated users to be tricked into submitting unintended requests to the plugin, potentially modifying membership settings, user accounts, or other state-changing operations.

MitigationImplement anti-CSRF tokens (synchronizer token pattern) on all state-changing operations (forms, AJAX calls) and validate Origin/Referer HTTP headers to ensure requests originate from trusted sources.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Identify installed ARMember version
    Go to WordPress admin dashboard > Plugins > Installed Plugins. Locate either ARMember or ARMember Premium plugin and record the version number displayed.
    Affected if Version is below 4.0.6 for ARMember or below 6.7.1 for ARMember Premium
  2. Inspect membership forms for anti-CSRF token
    View the HTML source of any ARMember form (registration, profile update, subscription change). Look for a hidden input field containing a nonce value (typically named '_wpnonce', 'arm_nonce', or similar).
    Affected if No nonce or token field is present in state-changing forms
  3. Test form submission behavior without nonce
    Submit a test membership form request after removing any nonce token from the request parameters. Observe whether the action still completes successfully.
    Affected if Form submission succeeds without a valid nonce token, indicating missing CSRF protection
  4. Check AJAX handlers for nonce verification
    Review the plugin PHP files for AJAX action handlers (arm_ajax_ functions). Verify that each handler calls wp_verify_nonce or check_admin_referer before processing state-changing requests.
    Affected if AJAX handlers lack nonce verification before executing sensitive operations

A system is affected if the installed ARMember version is below 4.0.6 (or below 6.7.1 for Premium) AND state-changing forms or AJAX calls lack anti-CSRF token validation.

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.6 / 6.7.1 or later
Fixed in 4.0.66.7.1
Interim mitigation

Implement anti-CSRF tokens (synchronizer token pattern) on all state-changing operations (forms, AJAX calls) and validate Origin/Referer HTTP headers to ensure requests originate from trusted sources.

Recommended fix High confidence

ARMember 4.0.6+ or ARMember Premium 6.7.1+

  1. 1. Identify the currently installed version of ARMember or ARMember Premium in your WordPress installation
  2. 2. If using free version ARMember, upgrade to version 4.0.6 or later
  3. 3. If using premium version ARMember Premium, upgrade to version 6.7.1 or later
  4. 4. Verify the upgrade was successful by checking the plugin version number
  5. 5. Test that the plugin functionality remains intact after the upgrade

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

Fix this in Armember Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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