CVE-2022-4115: The Editorial Calendar WordPress plugin before 3.8.3 does not sanitise and escape its settings, allowing users

Q: How do I fix CVE-2022-4115?

editorial calendar: upgrade to newer than 3.7.12. Exact commands for each OS are on this page.

Q: Is CVE-2022-4115 being exploited?

CVE-2022-4115 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-4115 affect?

CVE-2022-4115 affects editorial calendar. Severity is medium (CVSS 5.4). The Editorial Calendar WordPress plugin before 3.8.3 does not sanitise and escape its settings, allowing users with roles as low as contributor to inject arbitrary web scripts in the plugin admin panel, enabling a Stored Cross-Site Scriptin

Q: How urgent is CVE-2022-4115?

Priority 34/100. Public exploit reference

Routine

MEDIUM 5.4UPGRADE

CVE-2022-4115 is a medium-severity flaw (CVSS 5.4) affecting editorial calendar. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Editorial Calendar WordPress plugin before 3.8.3 does not sanitise and escape its settings, allowing users with roles as low as contributor to inject arbitrary web scripts in the plugin admin panel, enabling a Stored Cross-Site Scripting vulnerability targeting higher privileged users.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	5.4 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	Required
EPSS exploit chance	0.4% (top 61%)
CISA exploited list	No
Published	2023-06-27
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: editorial calendar project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2023-06-27 14:15 UTCPublished CVE record published
2026-06-17 05:19 UTCUpdated Record last modified

editorial calendar project editorial calendar UPGRADE

Affected: <= 3.7.12

Fixed in: newer than 3.7.12

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy editorial-calendar || rpm -q editorial-calendar || editorial-calendar --version

2. UPGRADE to newer than 3.7.12 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade editorial-calendar

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade editorial-calendar

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-4115?

editorial calendar: upgrade to newer than 3.7.12. Exact commands for each OS are on this page.

Is CVE-2022-4115 being exploited?

CVE-2022-4115 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-4115 affect?

CVE-2022-4115 affects editorial calendar. Severity is medium (CVSS 5.4). The Editorial Calendar WordPress plugin before 3.8.3 does not sanitise and escape its settings, allowing users with roles as low as contributor to inject arbitrary web scripts in the plugin admin panel, enabling a Stored Cross-Site Scriptin

How urgent is CVE-2022-4115?

Priority 34/100. Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2023-36520 MEDIUM 5.4 UPGRADE Authorization Bypass Through User-Controlled Key vulnerability in MarketingFire Editorial Calendar.This issue
CVE-2013-10023 MEDIUM 6.3 UPGRADE A vulnerability was found in Editorial Calendar Plugin up to 2.6 on WordPress

References

← Back to latest CVEs