Security readout for executives and security teams
Plain-English summary
MF Gig Calendar for WordPress has a CSRF issue affecting versions through 1.2.1. An attacker would need user interaction to cause an unwanted action with limited integrity and availability impact. No active exploitation is identified in the provided sources.
Executive priority
Treat as a moderate website hygiene issue. Prioritize internet-facing WordPress sites using this plugin, especially where administrators are active, but do not treat it as confirmed active exploitation from the provided evidence.
Technical view
CVE-2024-33651 is CWE-352 in Matthew Fries MF Gig Calendar, package mf-gig-calendar, through 1.2.1. CVSS 3.1 is 5.4: network exploitable, low complexity, no privileges, user interaction required, no confidentiality impact, low integrity and availability impact.
Likely exposure
Exposure is limited to WordPress sites running MF Gig Calendar versions up to and including 1.2.1. Sites without this plugin are not indicated as affected in the provided bundle.
Exploitation context
The sources identify CSRF, not a standalone remote compromise. Successful abuse likely depends on social engineering a user into triggering an unintended request. KEV is false, and the bundle provides no evidence of active exploitation.
Researcher notes
Evidence is sparse: the bundle names CSRF and affected versions but does not describe the vulnerable action, nonce behavior, proof of concept, or fixed version. Avoid assuming exploitability beyond CVSS and the advisory text.
Mitigation direction
- Inventory WordPress sites for mf-gig-calendar installations and versions.
- Check vendor, WordPress, and Patchstack guidance for a fixed release or official workaround.
- Update the plugin if an official fixed version is available.
- If no maintained fix exists, evaluate disabling or replacing the plugin.
Validation and detection
- Confirm whether MF Gig Calendar is installed on each WordPress site.
- Record installed versions and flag anything through 1.2.1.
- Review the CVE and Patchstack entries for any newly published remediation details.
- Validate changes in staging before production rollout.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-33651 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.