WordPress IVPAY Plugin SQL Injection and Authentication Bypass

The IVPAY payments WordPress plugin through 1.0.8 does not sanitise a value from its payment callback before using it in a SQL statement, and treats an empty API key, which is its own default, as valid authentication, allowing unauthenticated attackers to read arbitrary data from the database.

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 IVPAY payments WordPress plugin through version 1.0.8 contains a critical SQL injection vulnerability combined with a dangerous authentication bypass flaw. An attacker can exploit unsanitized payment callback parameters to inject arbitrary SQL commands, allowing complete database enumeration and data extraction. The vulnerability is compounded by the plugin's acceptance of empty API keys as valid authentication—using its own default value—which eliminates the need for legitimate credentials. Any website running this plugin becomes immediately accessible to unauthenticated attackers, making this a severe threat to e-commerce operations and customer data security. The high CVSS score of 9.3 reflects the ease of exploitation and catastrophic impact on confidentiality.

Casky's 323 matching security skills detect this attack pattern by mapping to MITRE ATT&CK techniques TA0001 (Initial Access) and TA0043 (Reconnaissance). Practitioners using Casky's Claude-powered analysis would observe detection signatures indicating SQL injection attempts through callback parameters (CWE-89 manifestation), coupled with authentication failures showing empty or default credential usage. The platform's extended reasoning would correlate these signals to identify reconnaissance activities—database schema probing and data exfiltration queries—that precede actual breach attempts. Security teams would see findings highlighting payment processing endpoints receiving malformed callbacks, unusual database query patterns in logs, and unauthenticated access to sensitive API endpoints, enabling rapid response before attackers establish persistent access.

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

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

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

Run the skill that detects this →

X Instagram LinkedIn