WordPress Stripe Plugin Credential Hijacking via Missing Auth Check

The Event Tickets and Registration plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the Stripe OAuth return endpoint in all versions up to, and including, 5.27.4. This makes it possible for unauthenticated attackers to overwrite the site's Stripe merchant credentials (access tokens, publishable keys, and account ID), diverting all subsequent payment processing to the attacker's Stripe account.

Casky was already ahead

This CVE exploits attack patterns that Casky's 283matched 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 Event Tickets and Registration plugin for WordPress contains a critical authorization bypass that allows unauthenticated attackers to modify Stripe OAuth credentials through an unprotected return endpoint. By exploiting missing capability checks, attackers can overwrite access tokens, publishable keys, and merchant account IDs, redirecting all payment processing to their own Stripe accounts. This affects any WordPress site running the vulnerable plugin versions up to 5.27.4—a particularly dangerous exposure given the ubiquity of both WordPress and payment processing in e-commerce and event registration workflows. Organizations relying on this plugin face immediate financial risk, as payment theft occurs transparently to legitimate merchants.

Casky's 283 matched security skills leverage Claude's extended reasoning to detect the attack patterns underlying this vulnerability across two primary MITRE ATT&CK techniques: TA0004 (Privilege Escalation) and TA0006 (Credential Access). Practitioners using Casky would identify detection patterns including: suspicious POST requests to Stripe OAuth endpoints lacking authentication headers, unusual modifications to WordPress options tables storing Stripe credentials, unexpected Stripe account configuration changes from unauthenticated sources, and mismatches between expected and actual Stripe merchant IDs in payment processing logs. The AI-driven analysis would correlate these indicators with the CWE-862 (Missing Authorization) root cause, flagging the specific plugin endpoint as an attack vector and recommending immediate patching, credential rotation, and review of payment routing logs to identify compromised transactions.

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 →

283 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-3174.

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

Access with Stolen Session Cookie

identity access management · low

Run

MITRE ATT&CK Techniques

TA0004 TA0006

Investigate the attack patterns behind CVE-2026-3174

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

Run the skill that detects this →

X Instagram LinkedIn