CVE-2025-67202 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in sidekiq-cron. A fix is available for sidekiq-cron — see the affected versions and patch details below.
Sidekiq-cron is vulnerable to a cross-site scripting (xss) vulnerability via crafted URL
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-67202.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
sidekiq-cronReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.
Description
Sidekiq-cron thru 2.3.1, an open-source scheduling add-on for Sidekiq, is vulnerable to a cross-site scripting (xss) vulnerability via crafted URL being rended from cron.erb.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 💎RubyGems | sidekiq-cron | all versions | 2.4.0bundle update sidekiq-cron --conservative |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sidekiq-cron, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update sidekiq-cron to 2.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-67202 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
To mitigate this issue, restrict network access to the Sidekiq-cron web interface to trusted users and networks only. Implement firewall rules to limit access to the port on which Sidekiq-cron is exposed. Additionally, ensure that users accessing the interface are aware of phishing risks and avoid clicking untrusted links.Source: Red Hat security advisory for CVE-2025-67202 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2025-67202 in your dependencies?
Find it across RubyGems, including transitive dependencies.