dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-44013

HIGH · 7.5 CVSS v3.1 Published 2024-10-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Innate Images LLC VR Calendar vr-calendar-sync allows PHP Local File Inclusion.This issue affects VR Calendar: from n/a through <= 2.4.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 confidence

The VR Calendar plugin contains a path traversal vulnerability in the vr-calendar-sync component that allows unauthenticated attackers to manipulate file path parameters and include arbitrary PHP files from the server, potentially leading to remote code execution.

MitigationUpgrade to a patched version of VR Calendar plugin (if available) or remove/disable the plugin until remediation is possible; implement strict input validation on file path parameters to prevent directory traversal.

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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

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. Verify VR Calendar plugin is installed
    Check the WordPress plugins directory for the vr-calendar folder. On typical installations, this is at /wp-content/plugins/vr-calendar/ or navigate to Plugins > Installed Plugins in WordPress admin and look for 'VR Calendar'
    Affected if VR Calendar plugin is present in the WordPress installation
  2. Identify the installed version
    Open the main plugin file (usually vr-calendar.php) and look for the Version header in the plugin comment block, or check the plugin version displayed in the WordPress admin plugins list
    Affected if Version cannot be determined or is earlier than the patched version
  3. Confirm vr-calendar-sync component exists
    Check for the vr-calendar-sync directory or file within the plugin folder at /wp-content/plugins/vr-calendar/vr-calendar-sync/
    Affected if The vr-calendar-sync component directory or files are present
  4. Check if the vulnerable file inclusion function is accessible
    Inspect the vr-calendar-sync PHP files for functions that handle file path parameters (such as include, require, include_once, or require_once with variable inputs). Test if the endpoint accepts path parameters without sanitization by examining the code for $_GET, $_POST, or similar superglobals used in file inclusion calls
    Affected if Code contains file inclusion functions using unsanitized input from request parameters
  5. Verify the endpoint is exposed to unauthenticated access
    Review the vr-calendar-sync component's access control settings in the PHP files. Check for missing capability checks or authentication requirements before the vulnerable function is called
    Affected if The vulnerable file inclusion functionality can be reached without authentication

If the VR Calendar plugin is installed with the vr-calendar-sync component present and the file inclusion function accepts unsanitized path parameters without authentication, the environment is affected by this path traversal vulnerability.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of VR Calendar plugin (if available) or remove/disable the plugin until remediation is possible; implement strict input validation on file path parameters to prevent directory traversal.

Recommended fix Moderate confidence

VR Calendar version 2.4.1 or later (check WordPress plugin repository for latest release)

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to the WordPress admin dashboard and go to Plugins > Installed Plugins.
  3. 3. Locate the 'VR Calendar' plugin and check its current version (should be <= 2.4.0).
  4. 4. Update the VR Calendar plugin to the latest available version (look for version 2.4.1 or higher in the WordPress plugin repository).
  5. 5. If no update is available in the WordPress admin, visit the official WordPress plugin repository and manually download the latest version of VR Calendar.
  6. 6. Deactivate the existing VR Calendar plugin, then delete it, and upload/install the newer version.
  7. 7. After updating, verify the plugin version shows 2.4.1 or higher.
  8. 8. Test the calendar functionality to ensure the update did not break expected features.
Caveat Minimal risk - patch releases typically contain only bug/security fixes; test in staging if concerned about compatibility

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-44013 — 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-2024-44013 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