CVE-2023-6360: The 'My Calendar' WordPress Plugin, version < 3.4.22 is affected by an unauthenticated SQL injection vulnerabi

Q: How do I fix CVE-2023-6360?

my calendar: upgrade to 3.4.22. Exact commands for each OS are on this page.

Q: Is CVE-2023-6360 being exploited?

CVE-2023-6360 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-2023-6360 affect?

CVE-2023-6360 affects my calendar. Severity is high (CVSS 8.6). The 'My Calendar' WordPress Plugin, version < 3.4.22 is affected by an unauthenticated SQL injection vulnerability in the 'from' and 'to' parameters in the '/my-calendar/v1/events' rest route.

Q: How urgent is CVE-2023-6360?

Priority 65/100. High severity; EPSS top 1%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 8.6REMOTEUPGRADE

CVE-2023-6360 is a high-severity flaw (CVSS 8.6) affecting my calendar. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The 'My Calendar' WordPress Plugin, version < 3.4.22 is affected by an unauthenticated SQL injection vulnerability in the 'from' and 'to' parameters in the '/my-calendar/v1/events' rest route.

Why this priority

High severity
EPSS top 1%: very likely to be exploited
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	8.6 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	63.1% (top 1%)
CISA exploited list	No
Weakness	CWE-89
Published	2023-11-30
Last modified	2026-06-17

Publisher (CNA): Tenable Network Security, Inc. · Vendor: joedolson

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

Am I affected?

Timeline

2023-11-30 16:15 UTCPublished CVE record published
2026-06-17 06:50 UTCUpdated Record last modified

joedolson my calendar UPGRADE

Affected: < 3.4.22

Fixed in: 3.4.22

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to 3.4.22 (Debian / Ubuntu)

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade my-calendar

Note

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

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Nuclei scan template: WordPress My Calendar <3.4.22 - SQL Injection

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-2023-6360?

my calendar: upgrade to 3.4.22. Exact commands for each OS are on this page.

Is CVE-2023-6360 being exploited?

CVE-2023-6360 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-2023-6360 affect?

CVE-2023-6360 affects my calendar. Severity is high (CVSS 8.6). The 'My Calendar' WordPress Plugin, version < 3.4.22 is affected by an unauthenticated SQL injection vulnerability in the 'from' and 'to' parameters in the '/my-calendar/v1/events' rest route.

How urgent is CVE-2023-6360?

Priority 65/100. High severity; EPSS top 1%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2024-1274 MEDIUM 5.4 UPGRADE The My Calendar WordPress plugin before 3.4.24 does not sanitise and escape some parameters, which could allow

References

← Back to latest CVEs