360 Orbit Security Digest

By Jörg Liwa

0+ active installationsVersion 2.4.1

Updates, known vulnerabilities and file changes at a glance: one calm digest email instead of constant notices in wp-admin.

Description

Security Digest solves a small but annoying problem: WordPress scatters update notices all over the admin area — as a small number in the menu, as a banner on every screen, as a separate entry in the plugin list. If you don’t open your site every day, they are easy to miss, and if you do, they keep interrupting you.

  • One digest email instead of constant notices: WordPress core, plugins and themes, each with the current and the new version.
  • Choose your own schedule: daily, weekly or monthly, plus weekday/time or day of the month.
  • Preview in the admin area before anything is sent.
  • Temporarily mute individual plugins in the digest (7/30/90 days).
  • Choose the digest language separately from the WordPress admin language.
  • “Send digest now” button for instant testing, including delivery diagnostics when sending mail fails.
  • Short sending history right in the admin area.
  • File check (optional, off by default): compares the files of WordPress and of your plugins from the WordPress.org directory with the official checksums and reports files that were changed, are missing or do not belong there. It never changes or deletes a file.
  • Weekly automatic file check once the file check is switched on (can be unticked).
  • Optional: check themes from WordPress.org against the package of the installed version.
  • Search for suspicious code: PHP files in the uploads folder and typical backdoor patterns (eval of decoded code, request data run as a command, code downloaders) in themes, must-use plugins and uploads. A heuristic, not a virus scanner; hits can be hidden once known.
  • “Security at a glance”: one box with the checks of all active 360 Orbit security plugins.
  • Vulnerability check (optional, off by default): compares the installed versions of WordPress, your plugins and your themes with the open vulnerability database WPVulnerability (by default once a night; twice a day or weekly if you prefer) and lists versions that are known to be affected, with the fixed version and a link to the source. A “Vulnerabilities” box on the overview and the WordPress dashboard says what to do, and a warning on every admin page stays until you mark the findings as done.
  • Hardening (each switch off by default): turn off the theme and plugin file editor, block access to wp-config.php and its backup copies, readme.html, license.txt and debug.log, switch off directory listings and the server signature, protect images against hotlinking. The rules go into their own block of the .htaccess file with a backup and a self-test that restores the previous version if the homepage answers with an error. A hint on file permissions that other users of the server could change.
  • The file check recognises the firewall file of Wordfence next to wp-config.php (name and content must match) and says whether it is in order or a leftover.
  • WP-CLI: send the digest, check its status, run the file check or the vulnerability check, even outside of wp-admin.

Free version vs. Pro

The free version fully covers the weekly digest email to one recipient.

Security Digest Pro adds:

  • Multiple recipient addresses instead of just one.
  • An instant security alert when an update looks security-relevant — instead of waiting for the next digest.
  • A summary of completed automatic WordPress updates in the same history.
  • File check on a schedule (daily or weekly), an email when a check finds something new, exceptions for individual files and a history of the checks.
  • Reinstall a package with findings at the push of a button: WordPress’s own installer puts the installed version back from WordPress.org. Files that do not belong to the package stay where they are.
  • File check for themes too, and for plugins without checksums: the files are compared with the package of the installed version from WordPress.org.
  • An email as soon as a new known vulnerability affects the website, and muting of individual entries for 30 or 90 days.
  • Slowing down conspicuous requests: counts REST API, admin-ajax.php, xmlrpc.php, search and 404 requests per visitor address and minute, and can answer with 429 above a limit. Starts in “only count” mode, with an allow list and an emergency switch.
  • Blocking by country and by block list: turn away visitors from selected countries (or allow only selected countries) and addresses on the Spamhaus DROP list or your own lists, for the login only, for single pages such as a contact form, or for the whole website. Starts in “only count” mode.
  • A request filter: recognises typical attack patterns in the content of a request (SQL injection, script injection, path tricks, scans for sensitive files, known scanning tools) and can turn such requests away. With an “only count” mode, exceptions per rule and address, an option to start early (as a must-use plugin, before other plugins load), signed rule updates without a plugin update and an option that forbids running PHP in the uploads folder. It also recognises fake search engines (Googlebot or Bingbot from an address that does not belong to them) and forms sent without browser identification and referring page. It is not a firewall with a maintained rule set.
  • Automatic temporary blocks: an address that sets off the request filter several times, asks for many pages that do not exist or clearly scans for sensitive files is blocked for 1 to 168 hours. Starts in “only count” mode; logged-in editors, the allow list and the website itself are never blocked.
  • A change log: who installed, activated, updated or deleted plugins and themes, changed users, roles or important settings, and when an administrator logged in. With filters, CSV export and a retention period. Passwords, keys and tokens are never stored.
  • Automatic update notifications right in the WordPress admin area.

External services

This plugin can connect to two external services. Both are optional and switched off by default. After activation alone, and after an update from an earlier version, the plugin contacts no server.

WordPress.org (file check)

Used to fetch the official checksums for the file check. Nothing is sent unless you switch on the file check under Security Digest → Files.

What is sent, and when:

  • When a file check runs (started by you, by WP-CLI or, in Pro, on a schedule): for WordPress itself the version and the language of the installed package, to api.wordpress.org/core/checksums/; for each installed plugin its folder name and version, to downloads.wordpress.org/plugin-checksums/.
  • The address of your website is not sent: the requests carry the plugin’s own user agent instead of the one WordPress uses by default.
  • No file contents are sent. The checksums are compared on your own server.
  • Only if you switch on “Also check themes from WordPress.org”: for each installed theme, the package of the installed version is downloaded from downloads.wordpress.org/theme/ (folder name and version). In Pro, the same happens for plugins without checksums (downloads.wordpress.org/plugin/). The package is only read, never unpacked or run, and deleted right after the comparison.

The service is provided by WordPress.org: Terms, Privacy Policy.

WPVulnerability (vulnerability check)

Used to find out whether an installed version is listed as affected by a known vulnerability. Nothing is sent unless you switch on the vulnerability check under Security Digest → Vulnerabilities.

What is sent, and when:

  • While the vulnerability check is switched on, once per package and run at the chosen interval (default: once a night) (in the background via WP-Cron, when you open the tab, or by WP-CLI): the WordPress version, to www.wpvulnerability.net/core/<version>/; the folder name of each installed plugin, to www.wpvulnerability.net/plugin/<name>/; the folder name of each installed theme, to www.wpvulnerability.net/theme/<name>/. Plugins that get their updates from another server and single-file plugins are not asked about.
  • The address of your website is not sent: the requests carry the plugin’s own user agent instead of the one WordPress uses by default.
  • The installed versions of plugins and themes are not sent. The comparison with the affected version ranges happens on your own server.

DB-IP and Spamhaus (Pro only)

The free version never contacts these services. In the Pro version, and only after you switch on “Blocking”, the website downloads the country database “IP to Country Lite” from download.db-ip.com once a month (if you selected countries) and the DROP list from www.spamhaus.org once a day (if you ticked it). Nothing about your website or your visitors is sent; the files are only downloaded. DB-IP licence, Spamhaus DROP terms.

The service is provided by WPVulnerability (vulnerability data under CC0 1.0): License and terms of use, Privacy Policy.

Installation

  1. Upload the plugin ZIP under Plugins → Add New → Upload Plugin.
  2. Activate the plugin.
  3. In the Security Digest menu, check the recipient, weekday and time under “Settings” (the defaults are already sensible: Monday, 8 am, to the admin email address).

FAQ

Do I need to install anything or set up an external service?

Not for the digest. It only reads the information WordPress already collects about updates on its own and sends it via wp_mail(). Only the optional file check (WordPress.org) and the optional vulnerability check (WPVulnerability) ask another server; both are off until you switch them on (see “External services”).

What does the vulnerability check tell me, and what not?

It tells you whether the installed version of WordPress, a plugin or a theme is listed as affected in the open database WPVulnerability, and which version fixes it if that is known. An entry does not mean your website was attacked, and an empty list is no proof of safety: the list is only as complete as its source. Paid and custom plugins and themes are usually not covered and are shown as “not checked”.

What does the file check tell me, and what not?

It tells you whether the files of WordPress and of your plugins from the WordPress.org directory are the ones that were published. A changed file is not proof of an attack: hosts, translations and manual fixes change files too. Paid plugins, themes, the uploads folder and the database are not part of the check and are shown as “could not be checked” or not at all. The plugin is not a malware scanner and not a firewall.

What happens when I deactivate the plugin?

The weekly sending cron is unscheduled immediately, so nothing is sent anymore, and the hardening block is removed from the .htaccess file. The previous sending history and all settings are kept and are back immediately after reactivating. Only “Delete” in the plugin list removes them permanently.

How reliable is the security alert (Pro)?

It is a best-effort, not a definitive assessment: the plugin searches the update notice that WordPress provides with an update for the word “security”. It does not replace your own review, but it is a useful early warning.

Which languages is the admin area available in?

The admin area follows the language set in WordPress. Translations are provided through translate.wordpress.org and you are welcome to contribute one for your language.

Screenshots

Changelog

2.4.1

  • New: hotlink protection for images on the Hardening tab.
  • The Pro version can also apply country and list blocking to single pages, such as a contact form.

2.4.0

  • New: Hardening tab: switch off the file editor, block sensitive files such as readme.html and debug.log, switch off directory listings and the server signature, with a self-test and automatic rollback.
  • New: a hint on file permissions that other users of the server could change.
  • New: the file check recognises the firewall file of Wordfence.
  • The Pro version can block scanning addresses automatically for a while and recognises fake search engines and forms sent without browser identification.

2.3.3

  • New: “Vulnerabilities” box on the 360 WP Orbit overview and the WordPress dashboard with affected packages and what to do.
  • New: warning on every admin page while there are open findings, until you mark them as done; a new finding brings it back. Can be switched off.
  • New: choose how often the vulnerability check runs: twice a day, once a day (default, at night) or once a week.

2.3.2

  • Changed: the “Security at a glance” box no longer mentions other plugins that are not installed.

2.3.1

  • Changed: the 360 WP Orbit overview shows the important boxes of the active plugins at the top, optionally also on the WordPress dashboard; all boxes and tables now use one width.

2.3.0

  • New: themes from WordPress.org can be checked against the package of the installed version (optional, off by default).

2.2.0

  • New: the file check runs automatically once a week when it is switched on.
  • New: search for suspicious code in the uploads folder, themes and must-use plugins (heuristic, nothing is sent).
  • New: “Security at a glance” box on the Status tab.

2.1.2

  • Maintenance release for the free version; the Pro version gains a setup assistant.

2.1.1

  • New: Quickstart on the Status tab switches on the file check and the vulnerability check in one click; in Pro also schedule, alerts, the change log and the protective functions in “Only count” mode (also wp 360-orbit-security-digest quickstart). Nothing is turned away.

2.1.0

  • This version brings every website to the complete state of 2.0.0: several parts of it were delivered step by step under the same version number, so earlier installations of 2.0.0 did not receive them as an update.
  • Changed: a tab with several boxes has one Save button that saves all fields of the tab.
  • New in Pro: the digest mentions how many requests were turned away or slowed down (only when a digest is sent anyway), and the change log notes the first rejection per day and rule.
  • Changed in Pro: an imported settings file never arms slowing down, blocking or the request filter; they arrive in “only count” mode.
  • The list on the “Security Digest Pro” tab names the new Pro functions.

2.0.0

  • New: file check. Compares the files of WordPress and of your plugins from the WordPress.org directory with the official checksums and reports files that were changed, are missing or do not belong there. Runs in small steps, can be paused and continued, and never changes or deletes a file.
  • New: vulnerability check. Compares the installed versions of WordPress, your plugins and your themes with the open database WPVulnerability once a day and lists versions that are known to be affected, with severity, CVE link and the fixed version.
  • Both checks are off by default: after the update nothing is sent until you switch them on under Security Digest > Files and Security Digest > Vulnerabilities.
  • New: lines in the digest when the last file check has findings, when known vulnerabilities affect the website or when the vulnerability source did not answer.
  • New: WP-CLI commands integrity (optionally for a single package) and vulnerabilities.
  • New: the 360 WP Orbit overview shows the last file check and the number of known vulnerabilities.
  • New in Pro: file check on a schedule (daily or weekly), an email when a check finds something new, exceptions for individual files with a reason, and a history of the last 20 checks.
  • New in Pro: “Reinstall package” next to a plugin or theme with findings. After a confirmation, WordPress’s own installer puts the installed version back from WordPress.org; files that do not belong to the package are kept.
  • New in Pro: file check for themes, and for plugins without checksums, against the package of the installed version from WordPress.org. The package is only read, never unpacked into the website and never run. Off by default.
  • New in Pro: an email when a new known vulnerability affects the website, and muting of individual entries for 30 or 90 days.
  • New in Pro: slowing down conspicuous requests (REST API, admin-ajax.php, xmlrpc.php, searches, 404 pages) per visitor address and minute, with an “only count” mode, an allow list, a live view and an emergency switch for wp-config.php. Off by default.
  • New in Pro: blocking by country and by block list (Spamhaus DROP, your own lists, fixed addresses), for the login, XML-RPC and the admin area or for the whole website, with an “only count” mode, an emergency switch for wp-config.php and a guard against locking yourself out. Off by default.
  • New in Pro: request filter with 16 general rules against typical attack patterns, each of which can be switched off, an “only count” mode, exceptions per rule and address (suggested in the admin area when one of your own requests would have been stopped), an emergency switch, and an option that forbids running PHP files in the uploads folder. Off by default. Not a firewall with a maintained rule set.
  • New in Pro: change log. Records who installed, activated, updated or deleted plugins and themes, changed users, roles or important settings, and when an administrator logged in. With filters, CSV export and a retention period of 30 to 365 days. Off by default. Passwords, keys and tokens are never stored, IP addresses only as a hash.
  • The readme now has an “External services” section for WordPress.org (checksums) and WPVulnerability.
  • New short description: updates, known vulnerabilities and file changes at a glance.

1.0.25

  • Changed: buttons, the License tab and Export/Import now look the same in all plugins of the suite (primary actions in the plugin colour, cards side by side).

1.0.24

  • New: the texts of the plugin appear in German by default, also on sites in another language; under 360 WP Orbit > Overview the language can be switched to the language of the website. The WordPress.org package follows the language of the website and now ships the German translation itself, so no language pack is needed.

1.0.23

  • Changed: tab order as in the other 360 Orbit plugins: Settings, then Export/Import, then License (or the Pro tab) at the end.
  • Changed: content boxes are 960 px wide as in the other 360 Orbit plugins and the License tab.

1.0.22

  • Changed: settings use the standard WordPress settings layout (one row per setting, label on the left, explanation below the field); frequency, day and time of the digest sit in one row.
  • Changed: in Pro, the recipient list and the fallback recipient have their own rows, and the security options have descriptive checkbox labels.
  • Changed: in Pro, the License tab uses the same layout; disconnecting has its own danger zone.

1.0.21

  • Updated: German translation completed (license server notice in Pro).

1.0.20

  • Changed: the 360 WP Orbit overview now picks up new suite plugins automatically, as every plugin registers itself. No more list to keep in sync.

1.0.19

  • New: the plugin list now shows a “Settings” link for this plugin, as it already does for the other plugins of the suite.

1.0.18

  • The brand name “360 WP Orbit” is no longer offered for translation, as it is the same in every language.

1.0.17

  • The 360 WP Orbit overview now also lists the new plugin 360 Orbit Database Cleaner.