CVE-2026-109931 Infility Global CVE debrief

Who should care

Defenders responsible for WordPress installations with the Infility Global plugin should assess exposure and prioritize verification and remediation efforts to prevent potential security breaches. This includes reviewing plugin versions, access restrictions, and monitoring for suspicious activity. Security teams and vulnerability management teams should also be aware of this vulnerability and take necessary actions to protect their systems.

Why it matters

Defenders should care about CVE-2026-109931 because it allows unauthenticated users to overwrite machine-translation configuration values in the Infility Global WordPress plugin, potentially leading to unauthorized modifications and exploitation.

• Potential unauthorized modifications to machine-translation configuration values
• Possible exploitation by unauthenticated users
• Need for verification of plugin version and access restrictions
• Potential impact on WordPress installations with the Infility Global plugin

Technical summary

The Infility Global WordPress plugin before 2.16.25 does not perform any authorisation or nonce check on an AJAX action available to unauthenticated users, allowing any visitor to overwrite a machine-translation configuration value belonging to a companion Infility Global WordPress plugin before 2.16.25. This vulnerability could lead to unauthorized modifications and potential exploitation. The plugin's lack of authorization and nonce checks on AJAX actions could allow unauthenticated users to modify machine-translation configuration values.

Defensive priority

Defenders should prioritize verifying the version of the Infility Global plugin and restricting access to the AJAX action to prevent unauthorized modifications.

Recommended defensive actions

• Verify the version of the Infility Global plugin and update to 2.16.25 or later
• Restrict access to the AJAX action to prevent unauthorized modifications
• Monitor for suspicious activity related to the Infility Global plugin
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the vulnerability, but additional information from the vendor and other sources may be necessary to fully assess the impact. The Infility Global plugin's lack of authorization and nonce checks on AJAX actions could allow unauthenticated users to modify machine-translation configuration values. This vulnerability may affect WordPress installations with the Infility Global plugin. Further verification and review of plugin versions, access restrictions, and monitoring for suspicious活动 are

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.