CVE-2024-58354 cal.diy vulnerability
cal.com (calcom repository, later renamed cal.diy) is affected by a repository takeover vulnerability in its GitHub Actions workflows. The workflow pr.yml uses the pull_request_target trigger with the repository's default write permissions and passes them down to check-types.yml. check-types.yml then performs a 'dangerous' checkout of the attacker-submitted pull request code (via the dangerous-git-checkout action) and subsequently executes it (through yarn install and package.json scripts). An attacker can open a pull request whose code runs arbitrary commands with the repository's write-scoped GITHUB_TOKEN, allowing them to push commits, merge or mutate pull requests, add or delete comments, and delete or force-push branches, thereby compromising the repository. The main branch is affected; no patched version is available.
Browse npm security risksQuick answer
calcom cal.diy should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- Review vendor advisory for affected versions.
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
CVE-2024-58354 affects cal.diy and involves code or command execution. Successful exploitation may let an attacker run unintended code or operating-system commands in the affected process. Prioritize internet-facing, privileged, automation, and production deployments. No confirmed fixed version is recorded for CVE-2024-58354; follow the linked vendor advisory, apply its mitigation, and update cal.diy as soon as a supported patched release is available.
- Inventory every deployment, device, package, plugin, container, build, and environment that uses cal.diy.
- Compare the installed package, build, firmware, or commit with the affected range in the linked vendor and NVD advisories.
- No confirmed fixed version is recorded for CVE-2024-58354; follow the linked vendor advisory, apply its mitigation, and update cal.diy as soon as a supported patched release is available.
- Until patched, disable the affected feature, limit untrusted input, and run the service with the lowest practical privileges.
- Review configuration, roles, tokens, network paths, and exposed endpoints connected to cal.diy; remove access that is not required.
- Review process, shell, web, audit, and network logs for unexpected commands, child processes, downloads, callbacks, or changed files.
- If exploitation is suspected, isolate affected assets, preserve evidence, rotate exposed credentials or keys, restore trusted data, and rebuild compromised systems before returning them to service.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm every affected asset now runs the fixed vendor-supported release or has the documented mitigation for CVE-2024-58354 in place.
- Use a safe regression test to confirm the affected code or command execution path no longer produces the vulnerable behavior.
- Confirm temporary access controls, endpoint restrictions, network blocks, and least-privilege settings remain effective after the update.
- Review post-remediation logs and rerun Fixnx plus the relevant package, dependency, firmware, browser, or product-specific security check.
- Document affected assets, versions, changes, validation evidence, reviewed logs, and any credential rotation, cleanup, or replacement completed.
Related categories
Related security risks
More published guidance from the same primary category.
Trusted references
FAQ
What is affected by CVE-2024-58354?
calcom cal.diy should be checked against the vendor advisory and trusted references linked on this page.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.