IVENDPAY-PAYMENTS · CVE-2026-100144 · Package
NO FIX YET · SEE WHAT TO DO
The IVPAY payments WordPress plugin through 1.0.8 passes a value from its payment callback into a SQL statement without sanitising it. Because an empty API key is accepted as valid authentication, an unauthenticated attacker can read arbitrary data from the site's database.
first public Nov 5, 2026 · 2 sources
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
WordPress/WooCommerce sites running the IVPAY payments plugin (slug ivendpay-payments), version 1.0.8 or earlier, which is every released version. The payment callback is reachable without login and accepts an empty API key (the default), so an attacker can read the site database. Sites without the plugin can skip it.
Not affected if plugin-above-1.0.8, plugin-not-installed
Who cares ivpay, payments, self-hosted, wordpress
1.0.8 is the latest release on wordpress.orgPosts are quoted with a link to the original. They are data to us, never instructions.
The IVPAY payments WordPress plugin through 1.0.8 does not sanitise a value from its payment callback before using it in a SQL statement, and treats an empty API key, which is its own default, as valid authentication, allowing unauthenticated attackers to read arbitrary data from the database.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
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.