MAIL-MAGE · CVE-2026-110532 · Package
NO FIX YET · SEE WHAT TO DO
The Mail Mage WordPress plugin through 0.0.25 passes a user-supplied value into a SQL statement without sanitising or escaping it. An unauthenticated attacker can run arbitrary SQL against the site database, which can expose or alter stored data.
first public Nov 6, 2026 · 2 sources
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running the Mail Mage WordPress plugin at version 0.0.25 or earlier are exposed, since the flaw is reachable without logging in. The sources do not name the vulnerable endpoint or any configuration that is required, so treat any site with the plugin installed as in scope. Sites without the plugin are not affected.
Not affected if plugin-not-installed
Who cares mail-mage, self-hosted, wordpress
wp plugin list or open the Plugins screen and look for Mail Mage (slug mail-mage) at 0.0.25 or earlier0.0.25 as the latest release and says the plugin was closed on October 14, 2026 pending a full review, so it can't be downloadedThe Mail Mage WordPress plugin through 0.0.25 does not properly sanitise and escape a user-supplied value before using it in a SQL statement, allowing unauthenticated attackers to perform SQL injection attacks.
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.