My Calendar Plugin Flaw (CVE-2026-104798)
If your WordPress site runs My Calendar – Accessible Event Manager version 3.8.7 or older, update the plugin to the latest version now, because CVE-2026-104798 is a critical flaw that lets a visitor with no login take over your main Administrator account.
This post is for owners of small WordPress sites who use My Calendar for events, classes or opening hours, and who do not want to read a wall of developer talk. You will get a plain-English explanation of the flaw, a quick way to see if you are affected, exact update steps, and a checklist for spotting signs of a break-in.
What was disclosed
The flaw is tracked as CVE-2026-104798. A CVE is a public ID number so everyone can refer to the same security bug. The record was published on 2026-10-16.
Here are the facts from the record:
| Item | Detail |
|---|---|
| Plugin | My Calendar – Accessible Event Manager (WordPress) |
| Affected versions | All versions up to and including 3.8.7 |
| Severity | Critical, CVSS score 9.8 out of 10 |
| Login needed to attack | None (unauthenticated) |
| Weakness type | CWE-269 (improper privilege management) |
| NVD status | Deferred |
The NVD page does not list affected versions as a separate field. The version range above comes from the written description in the record. The record also does not name a fixed version, so we will not guess one. Update to the latest release and read the changelog on the plugin's WordPress.org page.
How the flaw works, in plain English
This is a WordPress calendar plugin privilege escalation. Privilege escalation means someone gains more power on a site than they should have. Here, a stranger can end up as an Administrator, the account that controls everything.
Based on the record's description, the attack runs in these steps:
- The plugin accepts a public web address parameter called
mcs. Anyone can send a value in it, with no login. - The plugin puts that value into the page content without cleaning it first.
- WordPress then processes shortcodes in that content. A shortcode is a small tag in square brackets that tells WordPress to run a plugin feature.
- This lets an attacker slip in their own My Calendar shortcode with an
abovesetting. - The plugin splits that setting at the commas and runs each piece as the name of a PHP function. It does this with no check on who is asking and no list of allowed functions.
- The record describes a chain of calls that ends in WordPress's
edit_user()function acting on user ID 1. That overwrites the login details of the first Administrator account.
In short, the plugin trusted text from the internet and treated it like instructions. We are not publishing attack strings. You do not need them to fix this.
Why the score is 9.8
CVSS is a standard way to score how bad a bug is. The CVSS v3.1 specification defines the scale. This flaw scores near the top because of how easy it is to reach:
- It works over the internet (
AV:N). - It is low effort (
AC:L). - It needs no account (
PR:N). - It needs no click from a site owner or visitor (
UI:N). - It can hurt confidentiality, integrity and availability, which means your data, your content and your uptime (
C:H/I:H/A:H).
The record says the flaw is reachable through the plugin's auto-generated /my-calendar/ page, which is public by default once the plugin is activated. That is why a default install is the easy case for an attacker.
We have no confirmed information here about attacks happening in the wild. That is not a reason to wait. Public details make it easier for others to build attacks.
Who is affected
You should act if all of these are true:
- You use WordPress.
- My Calendar is installed and active.
- The version is 3.8.7 or lower.
An inactive plugin still sits on your server. The record talks about an activated plugin, but the safest move is to update it or delete it.
Step 1: check your version
In your dashboard, go to Plugins > Installed Plugins and find My Calendar – Accessible Event Manager. The version number is shown in the description line under the plugin name.
If you have command-line access with WP-CLI (WordPress's official command-line tool), run this:
wp plugin get my-calendar --fields=name,status,version
To see whether an update is pending, run this:
wp plugin list --name=my-calendar --fields=name,status,version,update_version
The plugin folder name my-calendar is the slug used in the vendor's code repository.
Step 2: update the plugin
Back up your site first. Your host's backup tool or a backup plugin is fine. Then update:
- Go to Dashboard > Updates or Plugins > Installed Plugins.
- Click Update now under My Calendar.
- Open your
/my-calendar/page and your event pages and confirm they still look right. - Check the version again. It should be higher than 3.8.7.
WP-CLI users can run:
wp plugin update my-calendar
If no update shows up, click Check Again on the Updates screen. Then read the changelog on the plugin page to see which release addresses this issue.
While you are there, turn on auto-updates for plugins you trust and need. In Plugins > Installed Plugins, click Enable auto-updates next to My Calendar. Auto-updates can occasionally break a site, so keep regular backups too.
If you cannot update right now
Sometimes a theme or custom code blocks a quick update. Here is how to cope:
| Situation | Safer action |
|---|---|
| No update visible yet | Deactivate the plugin until you can update. |
| Calendar is not business critical | Export or back up your events first, then deactivate and delete it. Deleting a plugin can remove its stored events. |
| You need it live today | Ask your host or a developer to block requests where the mcs parameter contains a square bracket, using a web application firewall (WAF, a filter that blocks bad web requests). |
You only hide the /my-calendar/ page | Do not rely on this alone. The record names that page as the easy route, not the only one. |
Treat a WAF rule as a short-term patch. It can miss variations. Updating or deactivating is the real fix.
Step 3: check whether anyone got in
Updating closes the door. It does not tell you whether someone walked through earlier. Because the flaw targets the first Administrator account, start there.
- Look at user ID 1. With WP-CLI:
wp user get 1 --fields=ID,user_login,user_email. Does the email look like yours? - List all administrators. Run
wp user list --role=administrator --fields=ID,user_login,user_email,user_registered, or open Users > All Users and filter by Administrator. Remove any account you do not recognize. - Watch for a lockout. If you can no longer log in as your usual admin, that is a warning sign. Ask your host to help you reset it, or use
wp user update 1 --prompt=user_passto set a new long, unique password. - Review plugins and themes. Open Plugins > Installed Plugins and Appearance > Themes. Delete anything you did not install.
- Check recent changes. Look for new pages, odd redirects, spam links, or unfamiliar files in
wp-content/uploads. - Search your access logs. Ask your host for raw logs, then search for requests that put square brackets in the parameter:
grep -i 'mcs=' access.log | grep -i -E 'my_calendar|%5Bmy_calendar'
%5B is how a browser writes [ in a web address. A match is not proof of a break-in, but it deserves a closer look. No match does not prove safety, since logs may be rotated or incomplete.
If anything looks wrong, change all admin passwords, log everyone out by replacing the secret keys (salts) in wp-config.php using the WordPress salt generator, and follow our website hacked guide. For a broader sense of how exposed a site can be, read Is my website hackable?.
What this teaches about plugin risk
The weakness here is a common type. The code did a powerful action without checking who was asking. OWASP lists this class of problem, broken access control, as its top web application risk.
You cannot read every plugin's code. You can lower your odds of trouble:
- Delete plugins you do not use.
- Keep WordPress, themes and plugins updated, and turn on auto-updates where sensible.
- Keep tested backups stored away from your web server.
- Avoid daily use of the Administrator account. Use an Editor account for routine work.
- Use a unique, long password plus two-factor login for every admin.
A free website security check can show what is visible to outsiders. It does not replace a human looking at how your plugins and settings fit together.
Key takeaways
- If My Calendar is at version 3.8.7 or older, update to the latest version today. Deactivate it if you cannot.
- The flaw (CVE-2026-104798, CVSS 9.8) needs no login and can lead to takeover of the first Administrator account.
- The NVD record gives no fixed version, so check the plugin changelog after updating.
- After updating, check your administrator list, recent changes and logs for signs of a past break-in.
- Remove unused plugins and turn on auto-updates to shrink future risk.
Want a human to look at your site?
If this alert made you wonder what else is lurking on your site, our $49 Circuit audit is the honest next step. A real security engineer manually reviews your site and sends a written report with severity, evidence and exact fixes. It is a focused small-site audit, not a compliance certificate or a multi-week enterprise pentest. See pricing, or compare approaches in manual vs automated testing.
Source: NVD entry for CVE-2026-104798.
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