Mf Gig CalendarWordPress extension · Mf Gig Calendar Project
CVE-2023-37970
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAuth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in Matthew Fries MF Gig Calendar plugin <= 1.2 versions.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA stored Cross-Site Scripting (XSS) vulnerability exists in the MF Gig Calendar WordPress plugin (versions 1.2 and below). Authenticated users with contributor-level permissions can inject malicious JavaScript code through calendar event inputs that get stored on the server and executed when other users view the affected content.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Mf Gig CalendarWordPress extension
< 1.2.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify MF Gig Calendar plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'MF Gig Calendar' in the list. Note whether it is active or inactive.Affected if The plugin is installed and active
-
Check the installed plugin versionIn the plugins list, click on 'MF Gig Calendar' to view details, or check the plugin files in wp-content/plugins/mf-gig-calendar/ for a version marker. Compare the version number to the affected range (versions below 1.2.1).Affected if The installed version is 1.2 or lower (below 1.2.1)
-
Identify contributor-level user accountsIn WordPress admin, go to Users > All Users and review the 'Role' column for any accounts with 'Contributor' role.Affected if At least one user account has Contributor role and the plugin is active
-
Inspect calendar event entries for suspicious contentNavigate to the MF Gig Calendar page in the admin or on the frontend where events are displayed. Review existing event entries for any unusual script tags, javascript: URLs, or HTML attributes containing event handlers (onclick, onerror, onload, etc.).Affected if Stored events contain unescaped HTML or script content that could execute JavaScript
You are affected if MF Gig Calendar plugin version 1.2 or below is active and contributor-level users can submit or have already submitted calendar events.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.2.1
Update the MF Gig Calendar plugin to the latest patched version. If no patched version is available, disable the plugin until a fix is released. Alternatively, restrict or disable contributor-level user creation pending a fix.
1.2.1 or later
- Update the MF Gig Calendar WordPress plugin to version 1.2.1 or later via the WordPress admin dashboard under Plugins > Updates, or download the latest version from the WordPress plugin repository
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Mf Gig Calendar
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37970 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-37970 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data