WordPress ARMember Plugin Stored XSS in Registration Fields

The ARMember Premium – Membership Plugin, Content Restriction, Member Levels, User Profile & User signup plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Registration Custom Field (Profile Cover) in all versions up to, and including, 7.8.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Casky was already ahead

This CVE exploits attack patterns that Casky's 323matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

The ARMember Premium membership plugin for WordPress contains a Stored Cross-Site Scripting (XSS) vulnerability in its registration custom field functionality, specifically the Profile Cover field. This vulnerability allows unauthenticated attackers to inject malicious JavaScript that persists in the database and executes whenever any user views the affected page. With a CVSS score of 7.2, this represents a high-severity risk affecting WordPress sites using ARMember up to version 7.8.1. The attack surface is particularly dangerous because it requires no authentication, meaning any visitor to the site can inject payloads, and the persistence of stored XSS means the malicious script will compromise legitimate users accessing normal site functionality.

Casky's 323 mapped security skills leverage Claude AI's extended reasoning to identify the attack patterns underlying this vulnerability across two critical MITRE ATT&CK techniques: TA0001 (Initial Access) and TA0043 (Reconnaissance). Practitioners using Casky would detect this vulnerability through pattern recognition of insufficient input sanitization in form fields and missing output escaping in user-controlled content rendering. The platform's skills would flag instances where user-supplied data from registration forms flows directly into page output without proper validation, recognizing the characteristic indicators of stored XSS including unescaped HTML entities, missing Content Security Policy headers, and registration workflows that lack input filtering. Security teams would see findings highlighting the specific attack chain: malicious script injection via the Profile Cover field → storage in the WordPress database → execution in victim browsers → potential session hijacking, credential theft, or malware distribution.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

323 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-93427.

Abuse of Public-Facing API: Mobile API Abuse

mobile security · low

Run

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

MITRE ATT&CK Techniques

TA0001 TA0043

Investigate the attack patterns behind CVE-2026-93427

Casky has 323 skills that investigate the attack patterns behind CVE-2026-93427. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn