CVE-2024-3756: The MF Gig Calendar WordPress plugin through 1.2.1 does not have CSRF checks in some places, which could allow

Q: How do I fix CVE-2024-3756?

mf gig calendar: upgrade to newer than 1.2.1. Exact commands for each OS are on this page.

Q: Is CVE-2024-3756 being exploited?

CVE-2024-3756 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-2024-3756 affect?

CVE-2024-3756 affects mf gig calendar. Severity is high (CVSS 7.5). The MF Gig Calendar WordPress plugin through 1.2.1 does not have CSRF checks in some places, which could allow attackers to make logged in Contributors and above delete arbitrary events via a CSRF attack

Q: How urgent is CVE-2024-3756?

Priority 37/100. High severity; Public exploit reference

Routine

HIGH 7.5UPGRADE

CVE-2024-3756 is a high-severity flaw (CVSS 7.5) affecting mf gig calendar. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The MF Gig Calendar WordPress plugin through 1.2.1 does not have CSRF checks in some places, which could allow attackers to make logged in Contributors and above delete arbitrary events via a CSRF attack

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.3% (top 75%)
CISA exploited list	No
Weakness	CWE-352
Published	2024-05-06
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: mf gig calendar project

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

Am I affected?

Timeline

2024-05-06 06:15 UTCPublished CVE record published
2026-06-17 07:44 UTCUpdated Record last modified

mf gig calendar project mf gig calendar UPGRADE

Affected: <= 1.2.1

Fixed in: newer than 1.2.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy mf-gig-calendar || rpm -q mf-gig-calendar || mf-gig-calendar --version

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

sudo apt update && sudo apt install --only-upgrade mf-gig-calendar

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade mf-gig-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-2024-3756?

mf gig calendar: upgrade to newer than 1.2.1. Exact commands for each OS are on this page.

Is CVE-2024-3756 being exploited?

CVE-2024-3756 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-2024-3756 affect?

CVE-2024-3756 affects mf gig calendar. Severity is high (CVSS 7.5). The MF Gig Calendar WordPress plugin through 1.2.1 does not have CSRF checks in some places, which could allow attackers to make logged in Contributors and above delete arbitrary events via a CSRF attack

How urgent is CVE-2024-3756?

Priority 37/100. High severity; Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2024-3755 MEDIUM 5.4 UPGRADE The MF Gig Calendar WordPress plugin through 1.2.1 does not sanitise and escape some of its settings, which co
CVE-2024-33651 MEDIUM 5.4 UPGRADE Cross-Site Request Forgery (CSRF) vulnerability in Matthew Fries MF Gig Calendar.This issue affects MF Gig Cal
CVE-2023-50842 HIGH 8.5 UPGRADE Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Matthew

References

← Back to latest CVEs