Hardcoded REST API Credentials Enable WooCommerce Payment Theft

The Fundiin cho WooCommerce WordPress plugin through 3.4.0 does not have proper authorisation on several of its REST API routes, relying instead on a credential that is identical on every installation, allowing unauthenticated attackers to disclose the store's payment credentials and customer order data, overwrite the payment gateway configuration so that payments are credited elsewhere, and mark unpaid orders as paid. The same missing authorisation also allows arbitrary script to be stored in a field which is output unescaped on the classic checkout, leading to unauthenticated stored XSS on stores that do not use the block-based checkout.

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 Fundiin cho WooCommerce plugin through version 3.4.0 contains a critical authorization bypass vulnerability affecting thousands of e-commerce sites. By relying on identical, hardcoded credentials across all installations rather than proper authentication mechanisms, the plugin exposes REST API endpoints that grant unauthenticated attackers direct access to sensitive payment processor credentials, customer order information, and payment gateway configurations. Any threat actor can exploit this without authentication, making it trivially easy to compromise store operations, redirect customer payments, and commit fraud at scale. This impacts every organization running the vulnerable plugin version, from small shops to larger merchants, with no warning or per-installation uniqueness to slow exploitation.

Casky's 283 mapped skills detect the attack patterns underlying this vulnerability through MITRE ATT&CK coverage of TA0004 (Privilege Escalation) and TA0006 (Credential Access). Practitioners using Casky would identify suspicious REST API calls lacking proper authorization headers, detection of hardcoded credential usage in API authentication patterns, and anomalous access to payment configuration endpoints from external sources. Claude's extended reasoning identifies how attackers move from initial reconnaissance of the REST API to credential exfiltration and lateral privilege escalation within the payment processing chain. Practitioners would see findings flagging unauthenticated API access to sensitive endpoints, unauthorized modifications to payment gateway settings, and indicators of customer data staging before exfiltration—allowing them to correlate these behavioral patterns and respond before financial impact occurs.

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-81649.

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-81649

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

Run the skill that detects this →

X Instagram LinkedIn