Editorial Calendar at a glance
- 5 publicly disclosed vulnerabilities, 1 of them rated High or Critical. The most recent was disclosed on Feb 15, 2026.
- Ranked #1366 by popularity on WordPress.org (20,000+ active installs).
- The latest version is 3.9.4 (released May 26, 2026). The most recent security fix shipped in 3.9.1.
- Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
- The first thing to do: update to the latest version and turn on automatic updates.
Check your Editorial Calendar version
Enter the Editorial Calendar version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.
Your version number is compared on this page only. It is not sent anywhere.
Get an email when a new vulnerability is disclosed
We'll tell you when a new vulnerability is disclosed in “Editorial Calendar”, with the version that fixes it. Free, email address only, stop any time.
We use your email address only for these alerts. Privacy policy
Want every plugin and theme on your site checked daily?
With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Editorial Calendar”.
- 2
Compare it with the list below
If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.
- 3
Update
Click “Update now” to move to the latest version (3.9.4). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known Editorial Calendar vulnerabilities
Editorial Calendar <= 3.9.0 - Authenticated (Contributor+) Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2026-32361
Affected versions: ≤ 3.9.0
Fixed in: 3.9.1
Severity: Medium 6.4 · Disclosed Feb 15, 2026
Editorial Calendar <= 3.8.8 - Missing Authorization
Missing authorization · CVE-2025-68603
Affected versions: ≤ 3.8.8
Fixed in: 3.8.9
Severity: Medium 4.3 · Disclosed Dec 20, 2025
Editorial Calendar <= 3.7.12 - Authenticated (Contributor+) Insecure Direct Object Reference
Missing authorization · CVE-2023-36520
Affected versions: ≤ 3.7.12
Fixed in: 3.8.0
Severity: Medium 5.4 · Disclosed Jun 27, 2023
Editorial Calendar <= 3.8.0 - Authenticated(Contributor+) Stored Cross-Site Scripting via edcal_saveoptions AJAX action
Cross-site scripting (XSS) · CVE-2022-4115
Affected versions: ≤ 3.8.0
Fixed in: 3.8.1
Severity: Medium 6.4 · Disclosed Jun 5, 2023
Editorial Calendar <= 2.6 - Authenticated (Admin+) SQL Injection
SQL injection · CVE-2013-10023
Affected versions: ≤ 2.6
Fixed in: 2.7
Severity: High 7.2 · Disclosed Feb 13, 2013
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| Editorial Calendar <= 3.9.0 - Authenticated (Contributor+) Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2026-32361 | ≤ 3.9.0 | 3.9.1 | Medium 6.4 | Feb 15, 2026 |
| Editorial Calendar <= 3.8.8 - Missing AuthorizationMissing authorization · CVE-2025-68603 | ≤ 3.8.8 | 3.8.9 | Medium 4.3 | Dec 20, 2025 |
| Editorial Calendar <= 3.7.12 - Authenticated (Contributor+) Insecure Direct Object ReferenceMissing authorization · CVE-2023-36520 | ≤ 3.7.12 | 3.8.0 | Medium 5.4 | Jun 27, 2023 |
| Editorial Calendar <= 3.8.0 - Authenticated(Contributor+) Stored Cross-Site Scripting via edcal_saveoptions AJAX actionCross-site scripting (XSS) · CVE-2022-4115 | ≤ 3.8.0 | 3.8.1 | Medium 6.4 | Jun 5, 2023 |
| Editorial Calendar <= 2.6 - Authenticated (Admin+) SQL InjectionSQL injection · CVE-2013-10023 | ≤ 2.6 | 2.7 | High 7.2 | Feb 13, 2013 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Feb 15, 2026.
Most common weaknesses in Editorial Calendar
Cross-site scripting (XSS)
2 issues
An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.
Missing authorization
2 issues
Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.
SQL injection
1 issue
Input such as a form field can be used to rewrite the queries the site sends to its database. Attackers use it to pull out customer, member or order data.
Frequently asked questions
Is Editorial Calendar safe to use?
Editorial Calendar is a well-known plugin with 20,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (3.9.4) and turn on automatic updates.
How do I find which version of Editorial Calendar my site is running?
In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.
Could updating break my site?
Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.
Can I check all my other plugins too?
Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.
Check every plugin and theme automatically, every day
Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.
Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.
← All plugin vulnerabilitiesEditorial Calendar on WordPress.org