[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f-22ZLToqKtyWe6I301gj23hVnUzHJaUmJ_aSRZdMugQ":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":13,"last_updated":14,"tested_up_to":15,"requires_at_least":16,"requires_php":17,"tags":18,"homepage":24,"download_link":25,"security_score":26,"vuln_count":27,"unpatched_count":13,"last_vuln_date":28,"fetched_at":29,"vulnerabilities":30,"developer":45,"crawl_stats":36,"alternatives":53,"analysis":157,"fingerprints":336},"developer-loggers-for-simple-history","Developer Loggers for Simple History","0.5.1","Pär Thernström","https:\u002F\u002Fprofiles.wordpress.org\u002Feskapism\u002F","\u003Cp>Bring more loggers to \u003Ca href=\"https:\u002F\u002Fsimple-history.com\" rel=\"nofollow ugc\">WordPress user history plugin Simple History\u003C\u002Fa>.\u003Cbr \u002F>\nThat are useful for developers during development of a site or to maintain a live site.\u003C\u002Fp>\n\u003Ch3>Important\u003C\u002Fh3>\n\u003Cp>Please note that this plugin is no longer actively maintained and only receives security fixes.\u003C\u002Fp>\n\u003Ch3>Modern and up to date alternatives\u003C\u002Fh3>\n\u003Cp>For an up to date alternative please see the \u003Ca href=\"https:\u002F\u002Fsimple-history.com\u002Fadd-ons\u002Fdebug-and-monitor\u002F\" rel=\"nofollow ugc\">Debug & Monitor add-on\u003C\u002Fa> which logs WP REST API requests, sent emails, HTTP API requests, and WP cron jobs.\u003C\u002Fp>\n\u003Ch3>Get more features with Simple History Premium\u003C\u002Fh3>\n\u003Cp>Need advanced WordPress audit logging capabilities? Simple History Premium extends your site monitoring with powerful features:\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Enhanced WordPress Activity Logging:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Advanced Analytics Dashboard\u003C\u002Fstrong> – Comprehensive stats and visual activity tracking\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Custom Event Logging\u003C\u002Fstrong> – Add manual entries and notifications to your audit trail\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Stealth Mode\u003C\u002Fstrong> – Control user access with granular permissions\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Flexible Log Retention\u003C\u002Fstrong> – Configure automatic cleanup or keep logs indefinitely\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Data Export Tools\u003C\u002Fstrong> – Export logs in CSV\u002FJSON format for analysis\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Security Features\u003C\u002Fstrong> – IP anonymization and login attempt location tracking\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fsimple-history.com\u002Fpremium\u002F\" rel=\"nofollow ugc\">» \u003Cstrong>Get Simple History Premium\u003C\u002Fstrong>\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch3>Included loggers and plugins\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>Post to Slack\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>All your events is posted to a \u003Ca href=\"https:\u002F\u002Fslack.com\u002F\" rel=\"nofollow ugc\">Slack\u003C\u002Fa> channel of your choice, using an \u003Ca href=\"https:\u002F\u002Fapi.slack.com\u002Fincoming-webhooks\" rel=\"nofollow ugc\">incoming webhook\u003C\u002Fa>. Yes, with this plugin enabled\u003Cbr \u002F>\nthere is no need what so ever to ever leave Slack to see what’s happening on your site or the site of your\u003Cbr \u002F>\nclients or… well, on any site where you have Simple Histor and this plugin enabled.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>WP_Mail-logger\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>See all mails sent with wp_mail(), no matter what the recipient address is.\u003Cbr \u002F>\nchangelog\u003C\u002Fp>\n\u003Cp>\u003Cstrong>404 logger\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>View page visits that load the 404 template.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>JavaScript error logger\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>See what JavaScript errors users that visit your site is getting.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>SystemLog logger\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Log all messages from Simple History to the syslog on the server. With this logger enabled there is no need to use the beautiful GUI of Simple History ;).\u003C\u002Fp>\n\u003Cp>\u003Cstrong>HTTP API logger\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Log all usage of HTTP calls from functions like wp_remote_post() and wp_remote_get().\u003C\u002Fp>\n\u003Cp>You can the URL requested, the arguments posted and the full returned result, including server headers.\u003C\u002Fp>\n\u003Cp>The time for the request to complete is also logged. Great for debugging!\u003C\u002Fp>\n","Useful loggers for SimpleHistory for developers during development of a site or to maintain a live site.",400,7569,0,"2025-09-15T07:32:00.000Z","6.4.8","4.4","",[19,20,21,22,23],"debugging","developer","email","logging","simple-history","https:\u002F\u002Fgithub.com\u002Fbonny\u002FDeveloper-Loggers-for-Simple-History","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdeveloper-loggers-for-simple-history.0.5.1.zip",99,1,"2025-09-16 00:00:00","2026-03-15T15:16:48.613Z",[31],{"id":32,"url_slug":33,"title":34,"description":35,"plugin_slug":4,"theme_slug":36,"affected_versions":37,"patched_in_version":6,"severity":38,"cvss_score":39,"cvss_vector":40,"vuln_type":41,"published_date":28,"updated_date":42,"references":43,"days_to_patch":27},"CVE-2025-10050","developer-loggers-for-simple-history-authenticated-admin-local-file-inclusion","Developer Loggers for Simple History \u003C= 0.5 - Authenticated (Admin+) Local File Inclusion","The Developer Loggers for Simple History plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 0.5 via the enabled_loggers parameter. This makes it possible for authenticated attackers, with Administrator-level access and above, to include and execute arbitrary .php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where .php file types can be uploaded and included.",null,"\u003C=0.5","medium",6.6,"CVSS:3.1\u002FAV:N\u002FAC:H\u002FPR:H\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:H","Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')","2025-09-17 01:49:16",[44],"https:\u002F\u002Fwww.wordfence.com\u002Fthreat-intel\u002Fvulnerabilities\u002Fid\u002Fb2ea3a9e-2a9a-4628-8ea1-e18e756f915f?source=api-prod",{"slug":46,"display_name":7,"profile_url":8,"plugin_count":47,"total_installs":48,"avg_security_score":49,"avg_patch_time_days":50,"trust_score":51,"computed_at":52},"eskapism",11,361040,91,1680,73,"2026-04-04T03:54:23.095Z",[54,79,103,120,138],{"slug":55,"name":56,"version":57,"author":58,"author_profile":59,"description":60,"short_description":61,"active_installs":62,"downloaded":63,"rating":64,"num_ratings":65,"last_updated":66,"tested_up_to":67,"requires_at_least":68,"requires_php":69,"tags":70,"homepage":74,"download_link":75,"security_score":76,"vuln_count":77,"unpatched_count":13,"last_vuln_date":78,"fetched_at":29},"check-email","Check & Log Email – Easy Email Testing & Mail logging","2.0.12","checkemail","https:\u002F\u002Fprofiles.wordpress.org\u002Fcheckemail\u002F","\u003Cp>In need of a tool that allows you to easily log and view all emails sent from WordPress? Check & Log might be just the solution for that.\u003Cbr \u002F>\nThis WordPress plugin helps you store sent emails for auditing purposes, as well as debug email related problems in your WordPress site. Works best on eCommerce websites that have been created with WooCommerce or Easy Digital Downloads.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fcheck-email.tech\u002F\" rel=\"nofollow ugc\">Home\u003C\u002Fa> | \u003Ca href=\"https:\u002F\u002Fcheck-email.tech\u002Fcontact\u002F\" rel=\"nofollow ugc\">Help & Tech Support\u003C\u002Fa> | \u003Ca href=\"https:\u002F\u002Fcheck-email.tech\u002Fdocs\u002F\" rel=\"nofollow ugc\">Documentation\u003C\u002Fa> | \u003Ca href=\"https:\u002F\u002Fcheck-email.tech\u002Fpricing\u002F#pro-feature\" rel=\"nofollow ugc\">Premium Features\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch3>New Features of the plugin Check & Log Email 2.0\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Export Logs\u003C\u002Fstrong> – It allows to export email logs in multiple file format with date range and status \u003Ca href=\"https:\u002F\u002Fcheck-email.tech\u002Fdocs\u002Fknowledge-base\u002Fhow-to-export-email-logs-in-check-log-email-plugin\u002F\" rel=\"nofollow ugc\">Learn More\u003C\u002Fa>. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>More Fields\u003C\u002Fstrong> – Such as Cc, Bcc, Host IP, Reply To etc. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Log Retention Period\u003C\u002Fstrong> – It allows to deletes old emails when a certain amount of logs and time has passed. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Print or save as PDF\u003C\u002Fstrong> – You can print the email log, or save it as a PDF. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Resend email\u003C\u002Fstrong> – This feature allow you to modify email and resend email. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Forward Email\u003C\u002Fstrong> – By using this feature you can automatically forward a copy of all emails sent by WordPress to other email addresses \u003Ca href=\"https:\u002F\u002Fcheck-email.tech\u002Fdocs\u002Fknowledge-base\u002Fforward-email-option-in-the-check-log-email-plugin\u002F\" rel=\"nofollow ugc\">Learn More\u003C\u002Fa>. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Easy migration\u003C\u002Fstrong> – It is allow you to import data from various plugins like Email Log, Mail logging – WP Mail Catcher, WP Mail Logging, WP Mail Log and export the data. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Email Error Tracking\u003C\u002Fstrong> – You can easily see list of errors of emails and view details of error. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Setup Wizard\u003C\u002Fstrong> – Wizard setup allows you to one time setup of this plugin. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Default Format for Message\u003C\u002Fstrong> – Its allow you to Default Format for Message on view of content. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>SMTP\u003C\u002Fstrong> – Its allow you to setup your own smtp through Check & Email Log SMTP form. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Multisite Configure\u003C\u002Fstrong> – Its allow to configure global setting for all your sites. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Encoding\u003C\u002Fstrong> – Its allow to encode emails and phone in page content. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Outlook \u002F MS 360\u003C\u002Fstrong> – Its allow to send email using 360 \u002F outlook configuration \u003Ca href=\"https:\u002F\u002Fcheck-email.tech\u002Fdocs\u002Fknowledge-base\u002Fmicrosoft-365-outlook-smtp-support-in-check-log-email\u002F\" rel=\"nofollow ugc\">Learn More\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Gmail SMTP\u003C\u002Fstrong> – Its allow to send email gmail configuration \u003Ca href=\"https:\u002F\u002Fcheck-email.tech\u002Fdocs\u002Fknowledge-base\u002Fgmail-smtp-support-in-check-log-email\u002F\" rel=\"nofollow ugc\">Learn More\u003C\u002Fa>. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Email Spam Testing\u003C\u002Fstrong> – Its allow to testing of your mail for accurate delivery \u003Ca href=\"https:\u002F\u002Fcheck-email.tech\u002Fdocs\u002Fknowledge-base\u002Fhow-to-use-the-email-spam-analyzer-an-essential-tool-for-every-e-commerce-store\u002F\" rel=\"nofollow ugc\">Learn More\u003C\u002Fa>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Features of the plugin Check & Log Email\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Test email sending\u003C\u002Fstrong> – if you’re not sure whether WordPress is sending emails, you can use this plugin to find out. The process is very simple: you need to choose an address that will receive a simple test email. You can even override the custom header with your own values, to avoid any other issues.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Viewing logged emails\u003C\u002Fstrong> – they can be viewed from the admin interface, as they are stored in a separate table. You get the option to filter them based on subject, email, date, etc.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Deleting logged emails\u003C\u002Fstrong> – you can delete them by going to the admin interface. You can either delete them in bulk or  selectively – by date, email, or subject. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Ability to change\u003C\u002Fstrong> the “mail from” email address, “mail from name” and override default email WordPress addresses.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Premium Features of the plugin Check & Log Email\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Triggered Data\u003C\u002Fstrong> – Triggered data helps you in debugging by showing the exact code that is sending that email \u003Ca href=\"https:\u002F\u002Fcheck-email.tech\u002Fdocs\u002Fknowledge-base\u002Fhow-to-use-the-trigger-option-to-debug-emails-by-identifying-the-exact-code\u002F\" rel=\"nofollow ugc\">Learn More\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Filters\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>wp_mail_catcher_mail_success\u003C\u002Fstrong> –  is triggered before an email is sent. It has a single argument that is an array containing original mail info.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>check_email_email_log_before_insert\u003C\u002Fstrong> –  is triggered before an email data about to save in check & Log Email. It has a two argument.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>log\u003C\u002Fstrong> –  It is an array containing argument that will store in database\u003C\u002Fli>\n\u003Cli>\u003Cstrong>original_mail_info\u003C\u002Fstrong> –   It is an array containing argument of original mail info.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>wp_check_email_failed\u003C\u002Fstrong> –  is triggered when an email is failed. It has a two argument.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>mail_error_data\u003C\u002Fstrong> –  It is an array containing argument that has what possible reasons of error.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>mail_error_message\u003C\u002Fstrong> –   It is an string containing error message.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Action\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>check_email_log_inserted\u003C\u002Fstrong> –  is triggered after data successfully saved in log.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>check_email_loaded\u003C\u002Fstrong> –  is triggered when check & log email successfully loaded.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Support\u003C\u002Fstrong>\u003Cbr \u002F>\nWe try our best to provide support on WordPress.org forums. However, We have a special \u003Ca href=\"https:\u002F\u002Fcheck-email.tech\u002Fcontact\u002F\" rel=\"nofollow ugc\">community support\u003C\u002Fa> where you can ask us questions and get help about your Check & Log Email related questions. Delivering a good user experience means a lot to us and so we try our best to reply each and every question that gets asked.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Bug Reports\u003C\u002Fstrong>\u003Cbr \u002F>\nBug reports for Check & Log Email are \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fahmedkaludi\u002Fcheck-email\" rel=\"nofollow ugc\">welcomed on GitHub\u003C\u002Fa>. Please note GitHub is not a support forum, and issues that aren’t properly qualified as bugs will be closed.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Credits\u003C\u002Fstrong>\u003Cbr \u002F>\n* jsPDF used https:\u002F\u002Fgithub.com\u002Fparallax\u002FjsPDF – License URI: https:\u002F\u002Fgithub.com\u002Fparallax\u002FjsPDF\u002Fblob\u002Fmaster\u002FLICENSE\u003Cbr \u002F>\n* league\u002Foauth2-client used https:\u002F\u002Fgithub.com\u002Fthephpleague\u002Foauth2-client – License URI: https:\u002F\u002Fgithub.com\u002Fthephpleague\u002Foauth2-client\u002Fblob\u002Fmaster\u002FLICENSE\u003C\u002Fp>\n","Check & Log email allows you to test if your website is correctly sending emails . Overriding of email headers and carbon copying to another address.",100000,2591078,96,281,"2026-03-03T12:29:00.000Z","6.9.4","5.0","5.6",[21,71,72,22,73],"email-log","log","smtp","https:\u002F\u002Fcheck-email.tech\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcheck-email.2.0.12.zip",97,5,"2024-03-25 00:00:00",{"slug":80,"name":81,"version":82,"author":83,"author_profile":84,"description":85,"short_description":86,"active_installs":87,"downloaded":88,"rating":89,"num_ratings":90,"last_updated":91,"tested_up_to":92,"requires_at_least":93,"requires_php":94,"tags":95,"homepage":99,"download_link":100,"security_score":101,"vuln_count":77,"unpatched_count":13,"last_vuln_date":102,"fetched_at":29},"wp-mail-catcher","Mail logging – WP Mail Catcher","2.1.11","JWardee","https:\u002F\u002Fprofiles.wordpress.org\u002Fwardee\u002F","\u003Cp>Logging your mail will stop you from ever losing your emails again! This fast, lightweight plugin (under 140kb in size!) is also useful for debugging or backing up your messages.\u003C\u002Fp>\n\u003Cp>Just install and activate then all of your contact form emails will be logged and saved to your DB with no additional configuration required.\u003C\u002Fp>\n\u003Cp>View and manage all your form submissions through the default WordPress interface. An email failed to send? With a single click you can resend the backed up email.\u003C\u002Fp>\n\u003Cp>Send emails out directly from the WordPress interface. Also includes support for attachments.\u003C\u002Fp>\n\u003Cp>Immediately find out if your contact form submission was successfully sent.\u003C\u002Fp>\n\u003Ch3>Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Zero setup required – just install and away you go\u003C\u002Fli>\n\u003Cli>Minimalistic – no overbloated features you never use weighing your site down – under 140kb in size!\u003C\u002Fli>\n\u003Cli>Bulk export emails to CSV for easy inclusion into Excel or any other program\u003C\u002Fli>\n\u003Cli>Compose new emails with the WordPress controls you’re already familiar with\u003C\u002Fli>\n\u003Cli>Resend your emails in bulk\u003C\u002Fli>\n\u003Cli>Debugging – see exactly which file and code line was responsible for sending the email, along with any errors encountered\u003C\u002Fli>\n\u003Cli>Manage what user permissions can see the logs\u003C\u002Fli>\n\u003Cli>Routinely have your logs cleared out at a specified time – or keep them forever\u003C\u002Fli>\n\u003Cli>Need to be notified when there’s a problem sending your mail? We’ve got hooks that allow you to do just that\u003C\u002Fli>\n\u003Cli>Completely free\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Hooks and actions\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ccode>wp_mail_catcher_mail_success\u003C\u002Fcode> is triggered when a message is sent and logged successfully. It has a single argument that is an array containing the log\n\u003Cul>\n\u003Cli>\u003Ccode>id\u003C\u002Fcode> related to the id in the \u003Ccode>mail_catcher_logs\u003C\u002Fcode> MySQL table\u003C\u002Fli>\n\u003Cli>\u003Ccode>time\u003C\u002Fcode> relative, readable time to when the log was saved\u003C\u002Fli>\n\u003Cli>\u003Ccode>email_to\u003C\u002Fcode> the email address(es) that the message was sent to\u003C\u002Fli>\n\u003Cli>\u003Ccode>subject\u003C\u002Fcode> the subject line of the message\u003C\u002Fli>\n\u003Cli>\u003Ccode>message\u003C\u002Fcode> the contents of the message\u003C\u002Fli>\n\u003Cli>\u003Ccode>status\u003C\u002Fcode> an integer depicting if the message was sent successfully or not (1 = sent successfully. 0 = sending failed)\u003C\u002Fli>\n\u003Cli>\u003Ccode>error\u003C\u002Fcode> the error that occurred – if any\u003C\u002Fli>\n\u003Cli>\u003Ccode>backtrace_segment\u003C\u002Fcode> a json_encoded object that shows which file and line the mail was initially triggered from\u003C\u002Fli>\n\u003Cli>\u003Ccode>attachments\u003C\u002Fcode> a list of any attachments that were sent along with the email\u003C\u002Fli>\n\u003Cli>\u003Ccode>additional_headers\u003C\u002Fcode> a list of any headers that were sent\u003C\u002Fli>\n\u003Cli>\u003Ccode>attachment_file_paths\u003C\u002Fcode> a list of the location of any attachments that were sent\u003C\u002Fli>\n\u003Cli>\u003Ccode>timestamp\u003C\u002Fcode> a unix timestamp of when the email was sent\u003C\u002Fli>\n\u003Cli>\u003Ccode>is_html\u003C\u002Fcode> a boolean, that will be true if the message is a html email and false if not\u003C\u002Fli>\n\u003Cli>\u003Ccode>email_from\u003C\u002Fcode> the from value of the email\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp_mail_catcher_mail_failed\u003C\u002Fcode> is triggered when a message failed to send and logged successfully. It has a single argument that is an array containing the log (same as the arguments for \u003Ccode>wp_mail_catcher_mail_success\u003C\u002Fcode>)\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp_mail_catcher_deletion_intervals\u003C\u002Fcode> is a filter that should return an array where each key is an amount of time in seconds, and the value is the label. Used to determine when a message has expired and should be deleted\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp_mail_catcher_before_success_log_save\u003C\u002Fcode> is a filter that is called just before a successful log is saved. It has a single argument that is the transformed log that will be saved – use this to alter the log before it’s saved. Returning \u003Ccode>false\u003C\u002Fcode> will stop the log from being saved. Also note that this is fired even when an email has errored, because all logs are initially saved as “successful” before being possibly updated with an error (if applicable). This is because of the way the \u003Ccode>wp_mail\u003C\u002Fcode> and \u003Ccode>wp_mail_failed\u003C\u002Fcode> are implemented in WordPress.\n\u003Cul>\n\u003Cli>\u003Ccode>time\u003C\u002Fcode> a unix timestamp of when the email was sent\u003C\u002Fli>\n\u003Cli>\u003Ccode>email_to\u003C\u002Fcode> the email address(es) that the message was sent to\u003C\u002Fli>\n\u003Cli>\u003Ccode>subject\u003C\u002Fcode> the subject line of the message\u003C\u002Fli>\n\u003Cli>\u003Ccode>message\u003C\u002Fcode> the contents of the message\u003C\u002Fli>\n\u003Cli>\u003Ccode>backtrace_segment\u003C\u002Fcode> an array that shows which file and line the mail was initially triggered from\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp_mail_catcher_before_error_log_save\u003C\u002Fcode>\n\u003Cul>\n\u003Cli>\u003Ccode>time\u003C\u002Fcode> a unix timestamp of when the email was sent\u003C\u002Fli>\n\u003Cli>\u003Ccode>email_to\u003C\u002Fcode> the email address(es) that the message was sent to\u003C\u002Fli>\n\u003Cli>\u003Ccode>subject\u003C\u002Fcode> the subject line of the message\u003C\u002Fli>\n\u003Cli>\u003Ccode>message\u003C\u002Fcode> the contents of the message\u003C\u002Fli>\n\u003Cli>\u003Ccode>backtrace_segment\u003C\u002Fcode> an array that shows which file and line the mail was initially triggered from\u003C\u002Fli>\n\u003Cli>\u003Ccode>error\u003C\u002Fcode> the error that occurred\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n","Stop from ever losing your emails again! This fast, lightweight plugin (under 140kb in size!) is also useful for debugging or backing up your messages",20000,252175,98,107,"2025-07-13T12:57:00.000Z","6.8.5","4.7","7.4",[71,96,97,22,98],"email-logger","email-logging","mail-logging","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-mail-catcher\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-mail-catcher.2.1.11.zip",95,"2024-09-27 00:00:00",{"slug":104,"name":105,"version":106,"author":107,"author_profile":108,"description":109,"short_description":110,"active_installs":111,"downloaded":112,"rating":113,"num_ratings":47,"last_updated":114,"tested_up_to":67,"requires_at_least":115,"requires_php":94,"tags":116,"homepage":118,"download_link":119,"security_score":113,"vuln_count":13,"unpatched_count":13,"last_vuln_date":36,"fetched_at":29},"log-emails","Log Emails","1.5.0","webaware","https:\u002F\u002Fprofiles.wordpress.org\u002Fwebaware\u002F","\u003Cp>Log emails to the WordPress database for later analysis. Access is restricted to administrators, and emails with WordPress passwords are obfuscated for security \u002F privacy. Useful for diagnosing lost email problems.\u003C\u002Fp>\n\u003Cp>Use this plugin with \u003Ca href=\"https:\u002F\u002Fshop.webaware.com.au\u002Fdownloads\u002Fdisable-emails\u002F\" rel=\"nofollow ugc\">Disable Emails\u003C\u002Fa> to divert all WordPress emails into logs, especially handy for developers.\u003C\u002Fp>\n\u003Cp>Logs are automatically purged after a defined period, set through a settings page in the WordPress admin. Setting the period to 0 prevents logs from being purged. Uninstalling the plugin purges all logs.\u003C\u002Fp>\n\u003Ch3>Translations\u003C\u002Fh3>\n\u003Cp>Many thanks to the generous efforts of our translators:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Czech (cs-CZ) — \u003Ca href=\"http:\u002F\u002Fwww.klusik.cz\u002F\" rel=\"nofollow ugc\">Rudolf Klusal\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>English (en_CA) — \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Flocale\u002Fen-ca\u002Fdefault\u002Fwp-plugins\u002Flog-emails\" rel=\"nofollow ugc\">the English (Canadian) translation team\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>English (en_GB) — \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Flocale\u002Fen-gb\u002Fdefault\u002Fwp-plugins\u002Flog-emails\" rel=\"nofollow ugc\">the English (British) translation team\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>French (fr-FR) — \u003Ca href=\"http:\u002F\u002Fwww.eticweb.ca\u002F\" rel=\"nofollow ugc\">Hugo Catellier\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Korean (ko_KR) — \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Flocale\u002Fko\u002Fdefault\u002Fwp-plugins\u002Flog-emails\" rel=\"nofollow ugc\">the Korean translation team\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>If you’d like to help out by translating this plugin, please \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Fprojects\u002Fwp-plugins\u002Flog-emails\" rel=\"nofollow ugc\">sign up for an account and dig in\u003C\u002Fa>.\u003C\u002Fp>\n","Log emails to the database, to enable email problem analysis",6000,55158,100,"2025-12-14T04:14:00.000Z","4.0",[21,71,22,117],"logs","https:\u002F\u002Fshop.webaware.com.au\u002Fdownloads\u002Flog-emails\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Flog-emails.1.5.0.zip",{"slug":121,"name":122,"version":123,"author":124,"author_profile":125,"description":126,"short_description":127,"active_installs":128,"downloaded":129,"rating":113,"num_ratings":77,"last_updated":130,"tested_up_to":131,"requires_at_least":132,"requires_php":17,"tags":133,"homepage":135,"download_link":136,"security_score":137,"vuln_count":13,"unpatched_count":13,"last_vuln_date":36,"fetched_at":29},"debug-bar-console","Debug Bar Console","0.3.1","Drew Jaynes","https:\u002F\u002Fprofiles.wordpress.org\u002Fdrewapicture\u002F","\u003Cp>Adds a PHP\u002FSQL console to the debug bar. Requires the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fdebug-bar\u002F\" rel=\"ugc\">Debug Bar plugin\u003C\u002Fa> (v0.5 or later).\u003C\u002Fp>\n","Adds a PHP\u002FSQL console to the Debug Bar. Requires the Debug Bar plugin.",1000,211737,"2024-10-27T20:43:00.000Z","6.7.5","3.1",[134,19,20],"console","http:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fdebug-bar-console\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-bar-console.0.3.1.zip",92,{"slug":139,"name":140,"version":141,"author":142,"author_profile":143,"description":144,"short_description":145,"active_installs":128,"downloaded":146,"rating":113,"num_ratings":147,"last_updated":148,"tested_up_to":92,"requires_at_least":17,"requires_php":17,"tags":149,"homepage":153,"download_link":154,"security_score":89,"vuln_count":155,"unpatched_count":13,"last_vuln_date":156,"fetched_at":29},"wp-reroute-email","WP Reroute Email","1.5.2","Sajjad Hossain","https:\u002F\u002Fprofiles.wordpress.org\u002Fmsh134\u002F","\u003Cp>This plugin intercepts all outgoing emails from a WordPress site, sent using the wp_mail() function, and reroutes them to a predefined configurable email address. This is useful in case where you do not want email sent from a WordPress site to reach the users. For an example, to resolve an issue you downloaded production database to your development site and you want no email is sent to production users when testing. You may enable this plugin in development server and reroute emails to your given email address.\u003C\u002Fp>\n\u003Cp>WP Reroute Email provides options for adding your own text or the recipients address at the bottom of the mail.\u003C\u002Fp>\n\u003Cp>You may also save a copy of the email to database and view them from the interface.\u003C\u002Fp>\n\u003Cp>Now, you will be able to disable rerouting based on the subject texts.\u003C\u002Fp>\n","This plugin reroutes all outgoing emails from a WordPress site (sent using the wp_mail() function) to a predefined configurable email address.",28119,9,"2025-07-06T06:59:00.000Z",[150,151,21,152],"developer-tool","development-server","mail","http:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fwp-reroute-email\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-reroute-email.1.5.2.zip",3,"2023-07-05 00:00:00",{"attackSurface":158,"codeSignals":286,"taintFlows":305,"riskAssessment":323,"analyzedAt":335},{"hooks":159,"ajaxHandlers":274,"restRoutes":282,"shortcodes":283,"cronEvents":284,"entryPointCount":285,"unprotectedCount":285},[160,166,171,174,176,179,185,188,193,198,203,207,211,213,218,222,226,231,235,240,243,245,249,252,256,259,263,267,271],{"type":161,"name":162,"callback":163,"file":164,"line":165},"action","admin_notices","closure","class.php",77,{"type":161,"name":167,"callback":168,"file":169,"line":170},"simple_history\u002Fadd_custom_logger","SimpleHistory_DeveloperLoggers_addCustomLogger","developer_loggers.php",33,{"type":161,"name":172,"callback":163,"file":169,"line":173},"admin_init",39,{"type":161,"name":162,"callback":163,"file":169,"line":175},43,{"type":161,"name":162,"callback":177,"file":169,"line":178},"SimpleHistory_DeveloperLoggers_oldVersionNotice",61,{"type":180,"name":181,"callback":163,"priority":182,"file":183,"line":184},"filter","simple_history\u002Fdeveloper_loggers\u002Fenabled_loggers",10,"examples.php",6,{"type":180,"name":186,"callback":163,"priority":182,"file":183,"line":187},"simple_history\u002Fdeveloper_loggers\u002Fslackit\u002Fsettings",19,{"type":161,"name":189,"callback":190,"priority":182,"file":191,"line":192},"hmbkp_backup_complete","on_hmbkp_backup_complete","loggers\\BackUpWordPress_pluginlogger.php",36,{"type":161,"name":194,"callback":195,"priority":182,"file":196,"line":197},"init","log_usage","loggers\\CPUUsageLogger.php",29,{"type":161,"name":199,"callback":200,"priority":182,"file":201,"line":202},"deprecated_function_run","log_function","loggers\\ErrorLog_Logger.php",52,{"type":161,"name":204,"callback":205,"priority":182,"file":201,"line":206},"deprecated_argument_run","log_argument",54,{"type":161,"name":208,"callback":209,"priority":182,"file":201,"line":210},"doing_it_wrong_run","log_wrong",55,{"type":161,"name":172,"callback":163,"file":201,"line":212},64,{"type":161,"name":214,"callback":215,"priority":182,"file":216,"line":217},"404_template","on_404_template","loggers\\FourOhFourLogger.php",51,{"type":161,"name":219,"callback":163,"file":220,"line":221},"wp_enqueue_scripts","loggers\\FrontEndClick_Logger.php",23,{"type":161,"name":223,"callback":224,"file":220,"line":225},"wp_footer","add_script",27,{"type":180,"name":227,"callback":228,"priority":182,"file":229,"line":230},"pre_http_request","on_pre_http_request","loggers\\HTTP_Logger.php",25,{"type":161,"name":232,"callback":233,"priority":182,"file":229,"line":234},"http_api_debug","on_http_api_debug",28,{"type":161,"name":236,"callback":237,"file":238,"line":239},"wp_head","add_js_to_header","loggers\\JSErrorLogger.php",42,{"type":161,"name":241,"callback":163,"priority":182,"file":242,"line":225},"xinit","loggers\\MiscTestLogger.php",{"type":161,"name":241,"callback":163,"file":242,"line":244},58,{"type":161,"name":246,"callback":247,"file":248,"line":230},"simple_history\u002Fdeveloper_loggers\u002Fbefore_plugins_table","settings","loggers\\Slackit.php",{"type":180,"name":250,"callback":251,"priority":113,"file":248,"line":234},"simple_history\u002Flog\u002Finserted","on_log_insert_context_slackit",{"type":180,"name":253,"callback":254,"file":248,"line":255},"simple_history\u002Fheader_initiator_use_you","__return_false",187,{"type":180,"name":257,"callback":254,"file":248,"line":258},"simple_history\u002Fuser_logger\u002Fplain_text_output_use_you",188,{"type":180,"name":260,"callback":261,"file":248,"line":262},"simple_history\u002Frow_header_date_output","__return_empty_string",191,{"type":180,"name":264,"callback":265,"priority":182,"file":266,"line":225},"simple_history\u002Flog_insert_context","on_log_insert_context","loggers\\SystemLog_Logger.php",{"type":161,"name":268,"callback":163,"file":269,"line":270},"phpmailer_init","loggers\\WPMailLogger.php",65,{"type":180,"name":272,"callback":163,"file":273,"line":187},"cfdb_form_data","loggers-tmp\\ContactFormDBLogger.php",[275,279],{"action":276,"nopriv":277,"callback":278,"hasNonce":277,"hasCapCheck":277,"file":238,"line":175},"simple_history_log_js_error",false,"log_error",{"action":276,"nopriv":280,"callback":278,"hasNonce":277,"hasCapCheck":277,"file":238,"line":281},true,44,[],[],[],2,{"dangerousFunctions":287,"sqlUsage":288,"outputEscaping":290,"fileOperations":13,"externalRequests":27,"nonceChecks":285,"capabilityChecks":13,"bundledLibraries":304},[],{"prepared":13,"raw":13,"locations":289},[],{"escaped":291,"rawEcho":184,"locations":292},8,[293,296,297,299,300,301],{"file":220,"line":294,"context":295},38,"raw output",{"file":238,"line":206,"context":295},{"file":248,"line":298,"context":295},93,{"file":248,"line":64,"context":295},{"file":248,"line":64,"context":295},{"file":302,"line":303,"context":295},"templates\\settings.php",69,[],[306],{"entryPoint":307,"graph":308,"unsanitizedCount":13,"severity":322},"\u003CSlackit> (loggers\\Slackit.php:0)",{"nodes":309,"edges":320},[310,315],{"id":311,"type":312,"label":313,"file":248,"line":314},"n0","source","$_POST",40,{"id":316,"type":317,"label":318,"file":248,"line":64,"wp_function":319},"n1","sink","echo() [XSS]","echo",[321],{"from":311,"to":316,"sanitized":280},"low",{"summary":324,"deductions":325},"The \"developer-loggers-for-simple-history\" plugin v0.5.1 presents a mixed security profile. On the positive side, it demonstrates good practices by exclusively using prepared statements for its SQL queries and has no known currently unpatched vulnerabilities. The taint analysis also shows no critical or high severity unsanitized flows, and there are no instances of dangerous functions or file operations, which are all strong indicators of a well-developed codebase.  However, significant concerns arise from the plugin's attack surface. It exposes two AJAX handlers, both of which lack authentication checks. This absence of authorization on entry points is a critical security oversight, potentially allowing unauthenticated users to trigger plugin functionalities. Furthermore, while nonce checks are present, the complete lack of capability checks on AJAX handlers is a major weakness. The plugin's vulnerability history, though currently clean, previously included a \"Path Traversal\" vulnerability, indicating a past pattern that, combined with the current unprotected AJAX endpoints, warrants careful attention. The external HTTP request, while not explicitly flagged as risky without further context, is another area that should be monitored.\n\nIn conclusion, while the plugin's internal code quality concerning SQL and taint analysis is commendable, the exposure of unprotected AJAX endpoints represents a substantial risk. The history of a path traversal vulnerability, even if patched, coupled with the current lack of authorization on these entry points, means that an attacker could potentially exploit these handlers. The plugin's security posture is therefore weakened by its attack surface management. Recommendations should focus on implementing robust authentication and authorization checks for all AJAX handlers.",[326,328,330,332],{"reason":327,"points":182},"AJAX handlers without auth checks",{"reason":329,"points":291},"AJAX handlers without capability checks",{"reason":331,"points":285},"External HTTP request",{"reason":333,"points":334},"Output escaping is not fully implemented",4,"2026-03-16T19:49:40.314Z",{"wat":337,"direct":343},{"assetPaths":338,"generatorPatterns":340,"scriptPaths":341,"versionParams":342},[339],"\u002Fwp-content\u002Fplugins\u002Fdeveloper-loggers-for-simple-history\u002Floggers\u002FFrontEndClick_Logger.php",[],[339],[],{"cssClasses":344,"htmlComments":345,"htmlAttributes":346,"restEndpoints":347,"jsGlobals":348,"shortcodeOutput":351},[],[],[],[],[349,350],"ajaxURL","selector",[]]