CVE-2026-75959 gopayplugins CVE debrief

Who should care

Defenders responsible for WordPress installations with the GoPay for WooCommerce plugin should assess exposure and prioritize patching or mitigating this vulnerability, especially for systems with shop manager-level access and above.

Why it matters

The GoPay for WooCommerce plugin for WordPress is vulnerable to SQL Injection, allowing authenticated attackers to extract sensitive information from the database. Defenders should prioritize patching or mitigating this vulnerability, especially for systems with shop manager-level access and above.

• Authenticated attackers with shop manager-level access and above can extract sensitive information from the database
• SQL Injection vulnerability can lead to data breaches and unauthorized access to sensitive information
• Patching or mitigating this vulnerability can prevent potential data breaches and unauthorized access

Technical summary

The GoPay for WooCommerce plugin for WordPress is vulnerable to SQL Injection via the 'log_table_filter' parameter in all versions up to, and including, 1.0.36. This makes it possible for authenticated attackers, with shop manager-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The vulnerability is caused by insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. Defenders should prioritize patching or mitigating this vulnerability, especially for systems with shop manager-level access and above, to prevent potential data breaches and unauthorized

Defensive priority

Defenders should prioritize patching or mitigating this vulnerability, especially for systems with shop manager-level access and above.

Recommended defensive actions

• Patch or upgrade the GoPay for WooCommerce plugin to a version that fixes the SQL Injection vulnerability
• Restrict access to the log_table_filter parameter to prevent authenticated attackers from appending additional SQL queries
• Monitor database activity for suspicious queries that may indicate exploitation of this vulnerability
• 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 vulnerability is caused by insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This information comes from the CVE Program record and the NVD vulnerability detail page.

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.