Modern Events Calendar SQL Injection Fix
If your site runs Modern Events Calendar Lite or Pro older than version 7.37.0, update the plugin to 7.37.0 or newer now, because it has a SQL injection flaw (CVE-2026-96534) that a logged-in user with a basic Subscriber account can abuse.
This post is for owners of WordPress sites that use Modern Events Calendar to list classes, shows, webinars or appointments. You will learn what the flaw is in plain English, who is really at risk, and the exact steps to check your version, update safely and look for warning signs. No security background needed.
What is the Modern Events Calendar vulnerability?
Modern Events Calendar (often shortened to MEC) is a popular WordPress plugin for building event calendars. According to the National Vulnerability Database (NVD) entry for CVE-2026-96534, both the Lite and Pro versions before 7.37.0 fail to clean up a parameter before using it in a database query.
A parameter is a value the plugin receives from a web request, like a search term or an ID number. The plugin should treat that value as plain data. Here, it can end up treated as part of the database command instead. That is called SQL injection.
The NVD record says the flaw lets authenticated users with minimal privileges (Subscriber and above) carry out SQL injection attacks. The weakness is classified as CWE-89, the standard label for this bug type.
What is SQL injection, in plain English?
Your WordPress site keeps its content, users and settings in a database. SQL is the language the site uses to ask the database questions. A normal question looks like: give me the events for next week.
In SQL injection, an attacker sneaks extra instructions into a value the site expected to be harmless. If the code does not clean that value first, the database may run the attacker's instructions too. The OWASP page on SQL injection explains the idea in more depth.
Think of a restaurant order slip. You write a dish name on it. SQL injection is like writing a dish name followed by an extra instruction to the kitchen, and the kitchen follows both.
How serious is it?
NVD lists the severity as High, with a CVSS score of 7.7. CVSS is a standard 0 to 10 scoring system for how bad a flaw is. The vector string in the record is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N. Here is what each part means:
| Part of the score | What it means for you |
|---|---|
| AV:N (network) | It can be attempted over the internet. The attacker does not need to be near your server. |
| AC:L (low complexity) | No special conditions or tricks are needed. |
| PR:L (low privileges) | The attacker needs a login, but a basic one is enough. |
| UI:N (no user interaction) | Nobody has to click a link or open anything. |
| S:C (scope changed) | The impact can reach beyond the plugin itself, to the wider database. |
| C:H (high confidentiality impact) | The main risk is reading data that should be private. |
| I:N, A:N | The score assumes no impact on data integrity or availability. |
In short: the scoring points to data exposure as the main risk. That could include things stored in your WordPress database, like user records. The NVD description does not give technical details of how the bug is triggered, and we will not guess at them here.
One more note. NVD currently shows the record's status as Deferred. That is a processing label on the database entry. It does not make the flaw less real, and the fix is still the same.
Who is affected?
The NVD record does not list a full range of affected versions. The description says Modern Events Calendar Lite and Modern Events Calendar Pro before 7.37.0 are affected. So the safe reading is: anything older than 7.37.0 needs updating.
Here is how to judge your own exposure:
| Your situation | Risk level | What to do |
|---|---|---|
| MEC Lite or Pro older than 7.37.0, and anyone can register an account | Highest | Update today. Check your user list. |
| MEC older than 7.37.0, with Subscriber-level or other logged-in accounts for customers or members (for example a shop or membership site) | High | Update today. Review the accounts that exist. |
| MEC older than 7.37.0, only trusted staff have logins | Lower, but still real | Update soon. A staff account could be stolen or reused. |
| MEC 7.37.0 or newer | Covered for this issue | Keep auto-updates or a monthly update habit. |
| MEC not installed | Not affected | Nothing to do for this CVE. |
The key point is the Subscriber role. Subscriber is the lowest WordPress role. Many sites hand it out automatically through a registration form or a membership plugin. Shop plugins such as WooCommerce use their own Customer role, and the NVD record only names Subscriber and above, so check how your site assigns roles. That is why a bug needing only a Subscriber login deserves quick attention.
How to fix it: update to 7.37.0 or newer
The NVD description names 7.37.0 as the version before which the plugin is affected, so updating to 7.37.0 or later is the action to take. Also read the plugin's changelog from the vendor for details on that release.
- Back up your site. Use your host's backup tool or a backup plugin. You need both files and database.
- Check your version. In the WordPress dashboard, go to Plugins > Installed Plugins and find Modern Events Calendar. The version number is under the name.
- Update. If you see an update link, click Update now. For Lite, updates come through the normal WordPress plugin updater. For Pro, updates usually come through the vendor's license system, so make sure your license is active and check the vendor's update instructions if no update shows.
- Confirm the new version. Reload the Plugins page and check it reads 7.37.0 or higher.
- Test your calendar. Open your events page, a single event and any booking form. Make sure they still work.
If you have command line access with WP-CLI (a tool for managing WordPress from a terminal), these commands help:
wp plugin list --fields=name,status,version,update | grep -i "modern"
wp plugin update modern-events-calendar-lite
The first command shows the installed version. The second updates the Lite plugin. The folder name of the Pro plugin can differ, so use the name shown in the first command's output.
If you cannot update right away, a web application firewall (a filter in front of your site) may help block some attacks. Treat it as a temporary cushion, not a fix. Only the update removes the flaw.
Reduce your exposure while you update
A few quick settings cut the risk from any low-privilege bug:
- Close open registration if you do not need it. Go to Settings > General and untick Anyone can register under Membership. Or run
wp option get users_can_registerand, if it returns 1 and you do not need signups,wp option update users_can_register 0. - Review your user list. Go to Users > All Users and sort by newest. Look for accounts you do not recognise, especially ones created in bursts. The command
wp user list --fields=ID,user_login,role,user_registeredshows the same thing for every account and role, so shop and membership accounts are included. - Delete accounts you do not need. Old test and spam accounts add risk for no benefit.
- Remove unused plugins. If you stopped using MEC, deactivate and delete it rather than leaving it dormant.
Has my site already been hit?
The verified source for this post does not say whether anyone is exploiting the bug, so we cannot tell you either way. The honest approach is to update first, then look for signs of trouble.
Things worth checking:
- New administrator accounts you did not create (Users > All Users, filter by Administrator).
- Password reset emails or login alerts you did not trigger.
- Odd entries in your host's access logs, such as many requests to event or calendar URLs from one account or IP address.
- Unexpected changes to pages, plugins or settings.
A SQL injection that only reads data can leave few visible traces, so a clean look does not prove nothing happened. If you find anything suspicious, follow our website hacked guide. As a precaution, consider resetting passwords for administrators and rotating any API keys or tokens that plugins store in your database. Changing the salts in wp-config.php will also log everyone out.
Is Modern Events Calendar safe to keep using?
Once updated to 7.37.0 or newer, this specific issue is addressed. Any plugin can have bugs, and finding and fixing them is normal. What matters is how quickly you apply the fix. Keep the plugin updated, and keep your total plugin count low.
A free outside check can show part of your picture. Our free website security check looks at things like technology, subdomains, DNS and email security on a domain you own. It is passive, so it will not find a flaw like this one. For a deeper picture of what a person can find that a scanner misses, read manual vs automated penetration testing.
Build a simple update habit
This bug is one of many plugin flaws that get published each month. You do not need to follow security news to stay safe. You need a routine:
- Turn on automatic updates for plugins you trust, from Plugins > Installed Plugins, using the Enable auto-updates link on each plugin.
- Keep daily or weekly backups stored away from your server.
- Use strong, unique passwords and two-factor authentication for admin accounts.
- Delete plugins and users you do not use.
- Once a quarter, review what is installed and what each account can do.
For general WordPress hardening, see the official WordPress security documentation. To understand how exposed a typical small site is, our guide on whether your website is hackable is a good next read.
Key takeaways
- Modern Events Calendar Lite and Pro before 7.37.0 have a SQL injection flaw, CVE-2026-96534, rated High (CVSS 7.7) on the NVD.
- A logged-in Subscriber account is enough, so sites with open registration, membership logins or customer logins should check their accounts and update first.
- Back up, then update to 7.37.0 or newer, and confirm the version on the Plugins page.
- Close open registration if you do not need it, and clean out unknown or unused accounts.
- After updating, check for unknown admin users and odd activity. A firewall can help in the short term but does not replace the update.
Want a human to look at your site?
Updating fixes this one plugin bug. It does not tell you what else is on your site. A Bug Circuit audit is a manual security test by a real person, ending in a written report with every issue, its severity, evidence and fix steps. Essential is $49 one-time for one website, and it is a small-site audit, not a compliance certification. See plans and pricing if you would like a second pair of eyes.
A real human security engineer audits your whole site by hand and sends a full report: every issue, its severity, and the exact fix. From $49, with a 14-day money-back guarantee.
See pricing