Infility Global Plugin up to 2.15.21 on WordPress Log Endpoint cross site scripting

Summaryinfo

A vulnerability classified as problematic was found in Infility Global Plugin up to 2.15.21. Impacted is an unknown function of the component Log Endpoint. Executing a manipulation can lead to cross site scripting. This vulnerability is tracked as CVE-2026-10734. The attack can be launched remotely. No exploit exists.

Detailsinfo

A vulnerability classified as problematic was found in Infility Global Plugin up to 2.15.21. This vulnerability affects an unknown function of the component Log Endpoint. The manipulation with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. As an impact it is known to affect integrity. CVE summarizes:

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.

The advisory is shared for download at wordfence.com. This vulnerability was named CVE-2026-10734 since 06/03/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1059.007.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-59921). Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• WordPress Plugin

Vendor

• Infility

Name

• Global Plugin

Version

• 2.15.0
• 2.15.1
• 2.15.2
• 2.15.3
• 2.15.4
• 2.15.5
• 2.15.6
• 2.15.7
• 2.15.8
• 2.15.9
• 2.15.10
• 2.15.11
• 2.15.12
• 2.15.13
• 2.15.14
• 2.15.15
• 2.15.16
• 2.15.17
• 2.15.18
• 2.15.19
• 2.15.20
• 2.15.21

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion