LiveActive security incident?Get immediate response
CVE Record

CVE-2022-42888: WordPress ARMember Plugin <= 5.5.1 is vulnerable to Privilege Escalation

Unauth. Privilege Escalation vulnerability in ARMember premium plugin <= 5.5.1 on WordPress.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This CVE describes an unauthenticated privilege escalation issue in the ARMember premium WordPress plugin up to version 5.5.1. A successful attack could let an outsider gain elevated access to the site, with high confidentiality, integrity, and availability impact.

Executive priority

Treat this as urgent for any business website using ARMember. The issue can affect site control, customer data, and service availability, but urgency depends on whether the plugin is installed and vulnerable.

Technical view

The record maps to CWE-269 and carries CVSS 3.1 score 9.8: network attack vector, low complexity, no privileges, no user interaction, unchanged scope, and high CIA impact. The source bundle identifies ARMember premium plugin <= 5.5.1 as vulnerable.

Likely exposure

Exposure is most likely on internet-facing WordPress sites using the ARMember premium plugin at version 5.5.1 or older. The provided affected metadata is sparse, so teams should verify installed plugin name, edition, and version from their WordPress inventory.

Exploitation context

The supplied sources do not state active exploitation, and the CVE is not marked CISA KEV in the bundle. Risk remains high because the flaw is unauthenticated, remotely reachable, and privilege-escalating on public WordPress sites.

Researcher notes

Evidence is clear on vulnerability type, severity, and the <= 5.5.1 range, but incomplete on exploit details and fixed version. The bundle’s affected object lists version as n/a/default unaffected, while title and description identify <= 5.5.1.

Mitigation direction

  • Inventory WordPress sites for the ARMember premium plugin and installed version.
  • Check Patchstack and vendor guidance for the fixed or recommended safe version.
  • Upgrade or remove affected ARMember installations if vendor guidance confirms exposure.
  • Temporarily disable the plugin where affected status cannot be resolved quickly.
  • Prioritize public and revenue-critical membership sites first.

Validation and detection

  • Confirm whether ARMember premium plugin is installed on each WordPress site.
  • Record plugin version and compare it with the <= 5.5.1 vulnerable range.
  • Review WordPress admin users for unexpected privileged accounts.
  • Check site logs for unusual account creation or role changes.
  • Document remediation status and remaining unknown plugin versions.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-269: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-42888 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2022-42888Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ReputeinfosystemsARMembern/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-269 · source CWE mapping

Improper Privilege Management

Improper Privilege Management represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.