dbcve.org
Mf Gig CalendarApplication · Mf Gig Calendar Project

CVE-2021-24510

MEDIUM · 6.1 CVSS v3.1 Published 2021-09-13
Fix available
A fix is available. Upgrade to after 1.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
The MF Gig Calendar WordPress plugin before 1.2 does not sanitise and escape the id GET parameter before outputting back in the admin dashboard when editing an Event, leading to a reflected Cross-Site Scripting issue

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 · high confidence

The MF Gig Calendar WordPress plugin before version 1.2 does not sanitise and escape the id GET parameter before outputting it back in the admin dashboard when editing an Event, leading to a reflected Cross-Site Scripting (XSS) vulnerability.

MitigationUpdate the MF Gig Calendar plugin to version 1.2 or later which includes proper sanitization and escaping of the id parameter.

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 CalendarApplication
Affected:<= 1.1

CVSS 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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if MF Gig Calendar plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'MF Gig Calendar' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'mf-gig-calendar' or similar.
    Affected if The plugin is installed and active on the WordPress site
  2. Check the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find MF Gig Calendar, and view the version number displayed below the plugin name. Or check the plugin's main PHP file for the Version header in the plugin comment block.
    Affected if The version is 1.1 or lower (anything below 1.2)
  3. Verify admin access to event editing functionality
    Navigate to the plugin's admin section where events are managed (typically under a 'Gig Calendar' menu item in the WordPress admin sidebar). Locate the ability to edit an existing Event.
    Affected if User has administrative access to the WordPress dashboard and can access the event editor
  4. Test for reflected XSS in the id parameter
    While on the event editing page, observe the URL structure. If the page loads an event by ID (such as /wp-admin/admin.php?page=mf_gig_calendars&task=edit&id=XXX), manually add a test XSS payload to the id parameter (e.g., id=1"><script>alert(1)</script>) and check if the payload is reflected unescaped in the page HTML.
    Affected if The id parameter value is reflected in the page output without HTML encoding/sanitization

The environment is affected if the MF Gig Calendar plugin version is 1.1 or lower and the site has an administrator who can access the event editing functionality where the id parameter is used.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 1.1
Interim mitigation

Update the MF Gig Calendar plugin to version 1.2 or later which includes proper sanitization and escaping of the id parameter.

Recommended fix High confidence

1.2

  1. Back up your WordPress site before making any changes
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Find MF Gig Calendar in the plugin list
  4. Click Update Now to update to version 1.2 or later
  5. Verify the update was successful by checking the plugin version

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
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-24510 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-24510 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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