beat-scheduling
Warn
Audited by Snyk on Apr 13, 2026
Risk Level: MEDIUM
Full Analysis
MEDIUM W011: Third-party content exposure detected (indirect prompt injection risk).
- Third-party content exposure detected (high risk: 0.80). The skill explicitly ingests and acts on user-provided schedules (notably via django-celery-beat database PeriodicTask entries editable through Django Admin and the dynamic-schedules.py flow which loads an external JSON config from SCHEDULE_CONFIG_PATH), so untrusted/third‑party content is read at runtime and directly influences which tasks are registered and executed.
Issues (1)
W011
MEDIUMThird-party content exposure detected (indirect prompt injection risk).
Audit Metadata