CVE-2024-38716
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 · uneditedImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Blue Plugins Events Calendar for Google allows PHP Local File Inclusion.This issue affects Events Calendar for Google: from n/a through 2.1.0.
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 path traversal vulnerability in the Blue Plugins Events Calendar for Google WordPress plugin (versions through 2.1.0) allows remote attackers to perform local file inclusion by manipulating path sequences in plugin parameters, potentially exposing sensitive server files.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Identify if Events Calendar for Google plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins, or inspect the /wp-content/plugins/events-calendar-for-google/ directory via file system or FTPAffected if The plugin appears in the installed plugins list or the plugin directory exists on the server
-
Determine installed plugin versionIn WordPress admin, view the plugin details to see the version number, or check the main plugin file (e.g., events-calendar-for-google.php) for the 'Version:' header in the plugin comment blockAffected if The version number displayed is 2.1.0 or any earlier version
-
Verify vulnerable parameter handling existsInspect the plugin source code files, particularly any PHP files handling request parameters that construct file paths (look for functions like include, require, file_get_contents using user-supplied input without sanitization)Affected if Code contains path construction using $_GET, $_POST, or similar superglobals without proper validation of '../' sequences or use of realpath() normalization
-
Confirm web server exposure to path traversal parametersTest by submitting requests with '../' sequences in parameters that the plugin processes (common vulnerable parameter names may include 'file', 'path', 'template', 'page', or 'action'); also review access logs for suspicious '..' patternsAffected if The plugin processes file path requests from external sources and allows directory traversal sequences to pass through to file inclusion functions
You are affected if the Events Calendar for Google plugin is installed with version 2.1.0 or earlier and the vulnerable parameter handling code is present and accessible to web requests.
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.
From vendor dataUpdate the Events Calendar for Google plugin to the latest patched version once released, and implement input validation/sanitization to restrict path traversal sequences in user-supplied parameters.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-38716 — 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-2024-38716 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