CVE-2026-114451 · Package
NO FIX YET · SEE WHAT TO DO
The Membership Plugin for WordPress before 4.0.6 runs a database maintenance routine without any authorization or CSRF check. An unauthenticated visitor can trigger it to convert the plugin's tables to a narrower character set, irreversibly replacing 4-byte characters such as emoji in membership, discount code and payment records with question marks.
first public Nov 15, 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 Membership Plugin for WordPress below version 4.0.6 are exposed, because the vulnerable routine can be triggered by anyone without logging in. The damage is to stored membership, discount and payment records, so sites selling memberships are most affected. Sites without the plugin or already on 4.0.6 or later can skip it.
Not affected if plugin-not-installed, version-4.0.6-or-later
Who cares membership-plugin, self-hosted, wordpress
4.0.6 or later (the sources state the plugin is fixed in versions from 4.0.6).The Membership Plugin WordPress plugin before 4.0.6 does not perform any authorization or CSRF check before running a schema-altering database maintenance routine, allowing unauthenticated users to convert the Membership Plugin WordPress plugin before 4.0.6's own tables to a narrower character set, which irreversibly replaces every 4-byte character (such as emoji and some CJK characters) in the membership level, discount code and payment records with a question mark.
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.