{{> header.html page_title="WordPress Cron Tasks" header_widgets="" }} {{> threat/free_common.html }}
Cron events run tasks at set times. They're a common malware re-infection vector — a single hidden hook pointed at a malicious file can put your site back in a bad state minutes after cleanup. This preview shows the cron entries BitFire can read, but does not score them yet.
Callback resolution is unavailable, so this preview may show fewer details. For full accuracy, view this page from the WordPress admin dashboard.
Events scheduled with wp_schedule_event(). This preview lists the hooks BitFire read from WordPress,
but does not classify or verify them yet.
A malware scan is still required for full cron verification. Until then, cron entries are shown without pass/fail results.
| Hook | Execution interval | Status |
|---|---|---|
|
{{- data.hook }}
|
{{- data.schedule }} | Status: not checked |
No WP-Cron events found.
Either nothing is scheduled, or no WordPress cron events were available to preview.
Entries from the web-server user's crontab. This preview lists the system cron entries BitFire can read, but does not classify or verify them yet.
No readable system cron files.
Web-server user: {{- system_user }}
No user crontab entries.
The system crontab is reachable but contains no scheduled jobs.
| Source | Entry | Status |
|---|---|---|
| {{- data.source }} | {{- data.line }} |
Status: not checked |
For compromised WordPress sites, this is the most common source of re-infection and can lie dormant for months. Purchase BitFire PRO to audit all cron events and locate code that is re-infecting WordPress.