LiveActive security incident?Get immediate response
CVE Record

CVE-2023-3011: ARMember <= 4.0.5 - Cross-Site Request Forgery

The ARMember plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 4.0.5. This is due to missing or incorrect nonce validation on the arm_check_user_cap function. This makes it possible for unauthenticated attackers to perform multiple unauthorized actions via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-3011 affects the ARMember WordPress membership plugin through version 4.0.5. A malicious actor could trick a site administrator into clicking a crafted link, causing unauthorized administrative actions. The issue requires administrator interaction, but the potential integrity impact is high.

Executive priority

Handle as a moderate-priority WordPress plugin risk. It is not documented as actively exploited here, but affected sites could suffer unauthorized administrative changes if an administrator is successfully targeted.

Technical view

ARMember has a cross-site request forgery weakness in arm_check_user_cap because nonce validation is missing or incorrect. The published CVSS 3.1 score is 6.5, with network attack vector, no attacker privileges required, required user interaction, and high integrity impact.

Likely exposure

Exposure is limited to WordPress sites running ARMember versions up to and including 4.0.5. Sites without ARMember, or with versions not covered by the published affected range, are not indicated as affected by the source bundle.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. Practical exploitation depends on convincing a site administrator to take an action such as clicking a link, then abusing the missing CSRF protection.

Researcher notes

The key control failure is CSRF protection around arm_check_user_cap. The available sources identify the vulnerability class, affected version ceiling, CVSS vector, and a WordPress Trac changeset reference, but do not provide complete operational impact details.

Mitigation direction

  • Inventory WordPress sites using ARMember and record installed plugin versions.
  • Upgrade ARMember according to vendor or WordPress.org guidance.
  • Prioritize any installation running version 4.0.5 or earlier.
  • Limit WordPress administrator access to trusted users.
  • Review vendor release notes for the referenced nonce validation change.

Validation and detection

  • Check whether ARMember is installed on each WordPress site.
  • Confirm the installed ARMember version is newer than 4.0.5 or vendor-approved.
  • Review plugin code or changelog for nonce validation around arm_check_user_cap.
  • Check admin activity logs for unexplained membership or configuration changes.
Prepared
Confidence
high
Sources
4

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-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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
cve · low confidence lookup

CVE-2023-3011 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
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

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

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
3Source 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
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2023-3011Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
reputeinfosystemsARMember – Membership Plugin, Content Restriction, Member Levels, User Profile & User signup0unaffected
Weakness

CWE details

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

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.