WordPress Infility Global Plugin Stored XSS via Log Endpoint

The Infility Global plugin for WordPress is vulnerable to Stored Cross-Site Scripting via /cf7_record Log Endpoint in all versions up to, and including, 2.15.21 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. The /cf7_records viewer is accessible to any authenticated user including those with Subscriber-level access, meaning the injected payload executes for any logged-in user who visits the records page.

Casky was already ahead

This CVE exploits attack patterns that Casky's 322matched 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 Infility Global WordPress plugin contains a Stored Cross-Site Scripting (XSS) vulnerability in its /cf7_records log endpoint that affects all versions up to 2.15.21. Due to insufficient input sanitization and output escaping, unauthenticated attackers can inject malicious JavaScript that persists in the database and executes whenever authenticated users—even those with minimal Subscriber-level access—view the affected log pages. This vulnerability is particularly dangerous because the injection point is accessible to any authenticated user, creating a lateral attack surface where low-privileged accounts can compromise higher-privileged users. The vulnerability impacts all WordPress installations using this plugin, making it a widespread concern for organizations relying on Contact Form 7 record logging functionality.

Casky's 322 mapped security skills leverage Claude AI's extended reasoning to detect attack patterns associated with TA0001 (Initial Access) and TA0043 (Reconnaissance) by analyzing input validation weaknesses and output encoding gaps across web applications. Practitioners using Casky would receive findings highlighting: (1) insufficient sanitization of user-supplied data flowing into the /cf7_records endpoint, (2) missing or incomplete output escaping when log data is rendered in the browser, (3) detection of script payload patterns in database logs and HTTP requests, and (4) identification of authentication bypass scenarios where Subscriber-level accounts access sensitive administrative log viewers. The platform's skill set would correlate these observations with CWE-79 patterns, enabling teams to pinpoint exact code locations requiring remediation and understand the chain of techniques an attacker would execute—from reconnaissance through persistence via stored payload injection.

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 →

322 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-10734.

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

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

Run the skill that detects this →

X Instagram LinkedIn