WP Log Action

WP Log Action has one disclosed vulnerability in the WordSec catalog, all reported in 2024; it is fixed as of September 2026. Their average CVSS score is 6.1, and the most serious one scores 6.1 out of 10.

The most common weakness is Cross-Site Scripting, behind 1 of the records (100%).

The one issue recorded for WP Log Action has a vendor fix available, so running the current release closes it.

All of these findings were reported by João Pedro Soares de Alcântara. WP Log Action is installed on roughly 30 WordPress sites, so each unpatched flaw has a wide blast radius. The current release is tested up to WordPress 6.8.8.

Strategic Overview

Avg CVSSMedium
6.1/ 10
Patch Coverage100%
Open

0

Fixed

1

Get automatic notifications for all WP Log Action vulnerabilities before they are exploited.

Highest severity on recordCVSS 6.1CVE-2025-24619

WP Log Action <= 0.51 - Reflected Cross-Site Scripting

Read the full analysis

Vulnerability Records

1 records
Plugin Profile
Latestv0.54

WP Log Action

webheadcoder

Author

webheadcoder

5.0(1)
100/100
Last Updated
2025-05-06 (1y ago)
Active Installs
30+
Downloads
4,997
Requires WP
5.3+
Requires PHP
0+
Tested up to
WP 6.8.8
Created
2016-10-04 (10y ago)

This plugin uses hooks in the opposite way most plugins do. You add do_action where you want to do some logging and this plugin will save it to the database only when active. Log Activity This plugin now logs plugin activity (when activated, deactivated, deleted, updated, installed), when wordpress is updated, and when functions are used wrong or deprecated. Example: do_action( 'wp_log_info', 'So far ok', 'Details of what is ok.' ); if ( $something_bad_happened ) { do_action( 'wp_log_error', 'This Happened!', 'Details of what happened.' ); ... } See Tools->Logs to view, delete, and export the logs on the admin side. Only users with the manage_options capability will have access. This plugin automatically logs deprecated and doing_it_wrong errors. The rest is what you add to your code. You can log what functions will be run for a specific action or filter. For example if you want to see what runs in the &#8216;init’ hook: function check_init_hook() { do_action( 'wp_log_debug_hook', 'init' ); } add_filter( 'init', 'check_init_hook', 0 ); The following are the different levels of logging to add to your code. You can use any level how you see fit, the descriptions of each level are just guidelines. Emergency System is unusable do_action( &#8216;wp_log_emergency’, $label, $message ); Alert Action must be taken immediately. do_action( &#8216;wp_log_alert’, $label, $message ); Critical Critical conditions. do_action( &#8216;wp_log_critical’, $label, $message ); Error Runtime errors that do not require immediate action but should typically be logged and monitored. do_action( &#8216;wp_log_error’, $label, $message ); Warning Exceptional occurrences that are not errors. do_action( &#8216;wp_log_warning’, $label, $message ); Notice Normal but significant events. do_action( &#8216;wp_log_notice’, $label, $message ); Info Interesting events. do_action( &#8216;wp_log_info’, $label, $message ); Debug Detailed debug information. do_action( &#8216;wp_log_debug’, $label, $message );

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C