Marcus Downing

I think this can most safely be achieved by exposing the information as a WordPress action hook.

First, it needs to decouple the version check from plugin_security_scanner_do_this_daily and plugin_security_scanner_options, into a function called something like plugin_security_scanner_get_vulnerabilities that returns an array of plugins and their vulnerabilities.

Then inside plugin_security_scanner_do_this_daily, call an action:


do_action('plugin_security_scanner_vulnerabilities', $vulnerabilities);


This would allow other plugins to hook into this action and put the information wherever they see fit. In my case, I’d write it to a file that could be picked up in a task run by the local Nagios agent.

Would you object if I were to fork the plugin, make the necessary changes and send you a pull request?

Cool. Drop me a line if you need a beta-tester. A lot of our clients are interested in security audit and related areas, so we have an interest in having a good to available for WordPress.

Correction to stop it interfering with the meta box’ title:

#poststuff #richtext_excerpt_editor_metabox div.inside {
  padding: 0;
  margin-top: 0px;
}

#poststuff #richtext_excerpt_editor_metabox .wp-editor-tabs {
  margin-top: -34px;
  margin-right: 36px;
}

#wp-excerpt-editor-container {
  border-width: 1px 0 0 0;
}