CVE-2026-116614 · Package
NO FIX YET
The WPMR Google Feed Manager plugin for WordPress and WooCommerce fails to escape the 'sourceId' parameter in SQL queries, so an attacker can append queries. An authenticated attacker with Editor-level access can use this to extract sensitive data from the site's database.
first public Nov 13, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Sites running the WPMR Google Feed Manager plugin at version 2.24.1 or earlier are exposed. Because the plugin grants the edit_feeds capability to the Editor role on activation, any user with the Editor role can exploit it, so sites with many editor accounts carry more risk. Sites without this plugin, or with it at a fixed version, can skip it.
Not affected if patched-version, plugin-not-installed
Who cares woocommerce, wordpress, wpmr-google-feed-manager
2.24.1 or earlier, which the description says is vulnerable.No fix yet, per the sources.
The WPMR Google Feed Manager for WooCommerce – Sell on Google Merchant Center & Shopping plugin for WordPress is vulnerable to generic SQL Injection via the 'sourceId' parameter in all versions up to, and including, 2.24.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with editor-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 plugin grants the edit_feeds capability to the Editor role on activation, meaning any Editor-level user satisfies the authorization checks and can exploit this vulnerability.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.