[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f5Z-HzunEQhke07-64hESPeCKyUFIkPobbVru6DkIMF0":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":14,"last_updated":15,"tested_up_to":16,"requires_at_least":17,"requires_php":18,"tags":19,"homepage":23,"download_link":24,"security_score":13,"vuln_count":25,"unpatched_count":25,"last_vuln_date":26,"fetched_at":27,"vulnerabilities":28,"developer":29,"crawl_stats":26,"alternatives":34,"analysis":124,"fingerprints":243},"custom-recovery-mode-email","Custom Recovery Mode Email","1.0.6","Jairo Ochoa","https:\u002F\u002Fprofiles.wordpress.org\u002Fjairoochoa\u002F","\u003Cp>Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with an automated email.\u003C\u002Fp>\n\u003Cp>But sometimes the message bothers people who don’t know how to handle with it and how to fix the bug which causes the crash.\u003C\u002Fp>\n\u003Cp>With \u003Cem>Custom Recovery Mode Email\u003C\u002Fem> now you can choose the right recipient email of the person who can deal with it.\u003C\u002Fp>\n\u003Cp>Optionally you can also set Email and Name sender.\u003C\u002Fp>\n\u003Ch3>Translations\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>English\u003C\u002Fli>\n\u003Cli>Español (España)\u003C\u002Fli>\n\u003Cli>Euskara (thanks to @garridinsi)\u003C\u002Fli>\n\u003Cli>Galego\u003C\u002Fli>\n\u003Cli>Svenska (thanks to @tobifjellner)\u003C\u002Fli>\n\u003C\u002Ful>\n","Change the recipient address when WordPress sends an email if a Fatal Error occurs.",90,2460,100,1,"2025-08-05T19:33:00.000Z","6.8.5","6.0","7.4",[20,21,22],"fatal-error","recovery-mode","recovery-mode-email","https:\u002F\u002Fwww.dixitalmedia.com\u002F#que-hacemos","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcustom-recovery-mode-email.zip",0,null,"2026-03-15T15:16:48.613Z",[],{"slug":30,"display_name":7,"profile_url":8,"plugin_count":31,"total_installs":32,"avg_security_score":13,"avg_patch_time_days":14,"trust_score":13,"computed_at":33},"jairoochoa",2,190,"2026-04-04T14:46:17.410Z",[35,52,72,90,107],{"slug":36,"name":37,"version":38,"author":39,"author_profile":40,"description":41,"short_description":42,"active_installs":43,"downloaded":44,"rating":25,"num_ratings":25,"last_updated":45,"tested_up_to":46,"requires_at_least":47,"requires_php":48,"tags":49,"homepage":50,"download_link":51,"security_score":13,"vuln_count":25,"unpatched_count":25,"last_vuln_date":26,"fetched_at":27},"disable-fatal-error-handler","Disable Fatal Error Handler","0.0.4","Jose Mortellaro","https:\u002F\u002Fprofiles.wordpress.org\u002Fgiuse\u002F","\u003Cp>Activating Disable Fatal Error Handler your website will not send any email in case of fatal errors.\u003C\u002Fp>\n\u003Cp>When you work on a website and you don’t want the administrators receive an email every time the website triggers a fatal error, just activate this plugin.\u003C\u002Fp>\n\u003Cp>Disable Fatal Error Handler adds a constant in wp-config.php. You would not need this plugin if you remembered that constant and you have access via FTP.\u003C\u002Fp>\n\u003Cp>In my case I prefer remembering “Disable Fatal Error Handler”, search it in the plugins page, install and activate it, and that’s it.\u003C\u002Fp>\n\u003Ch3>Help\u003C\u002Fh3>\n\u003Cp>If you need help open a thread on the support forum of this plugin.\u003Cbr \u002F>\nPlease, before posting enable the debugging in wp-config.php. Need a step-by-step guide? Read \u003Ca href=\"https:\u002F\u002Ffreesoul-deactivate-plugins.com\u002Fhow-to-enable-debugging-in-wordpress-a-step-by-step-guide\u002F\" rel=\"nofollow ugc\">this detailed tutorial\u003C\u002Fa> on \u003Ca href=\"https:\u002F\u002Ffreesoul-deactivate-plugins.com\u002Fhow-to-enable-debugging-in-wordpress-a-step-by-step-guide\u002F\" rel=\"nofollow ugc\">how to enable debugging in WordPress\u003C\u002Fa> to learn more.\u003C\u002Fp>\n","Your website will not send any email in case of fatal errors.",200,2626,"2025-12-05T08:48:00.000Z","6.9.4","4.6","5.6",[36],"https:\u002F\u002Fjosemortellaro.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdisable-fatal-error-handler.0.0.4.zip",{"slug":53,"name":54,"version":55,"author":56,"author_profile":57,"description":58,"short_description":59,"active_installs":60,"downloaded":61,"rating":13,"num_ratings":31,"last_updated":62,"tested_up_to":16,"requires_at_least":63,"requires_php":64,"tags":65,"homepage":70,"download_link":71,"security_score":13,"vuln_count":25,"unpatched_count":25,"last_vuln_date":26,"fetched_at":27},"fatal-plugin-auto-deactivator","Fatal Plugin Auto Deactivator – Never let a plugin break your site","1.1.0","Linkon Miyan","https:\u002F\u002Fprofiles.wordpress.org\u002Frudlinkon\u002F","\u003Cp>The Fatal Plugin Auto Deactivator plugin is a powerful tool designed to enhance the stability and reliability of your WordPress website. It automatically detects and deactivates plugins that cause fatal errors, preventing your entire site from crashing and becoming inaccessible.\u003C\u002Fp>\n\u003Ch3>Key Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Automatic Error Detection\u003C\u002Fstrong>: Monitors for fatal PHP errors in real-time using WordPress drop-in technology\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Smart Plugin Identification\u003C\u002Fstrong>: Identifies which plugin is causing the fatal error through stack trace analysis\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Instant Deactivation\u003C\u002Fstrong>: Automatically deactivates the problematic plugin during the shutdown phase\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Detailed Admin Notifications\u003C\u002Fstrong>: Provides clear notifications about which plugin was deactivated and why\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Persistent Error Logging\u003C\u002Fstrong>: Records detailed information about errors in a permanent log for troubleshooting\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Error Log Management Page\u003C\u002Fstrong>: Dedicated admin page to view, manage, and clear error logs with detailed history\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Zero Configuration\u003C\u002Fstrong>: Works right out of the box with no setup required\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Custom Error Page\u003C\u002Fstrong>: Displays a user-friendly error page with a reload button instead of the white screen of death\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Debug-Aware Display\u003C\u002Fstrong>: Shows detailed error information only when WP_DEBUG_DISPLAY is enabled for security\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Drop-in Management\u003C\u002Fstrong>: Automatically installs and manages WordPress fatal-error-handler.php drop-in\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>How It Works\u003C\u002Fh3>\n\u003Cp>This plugin uses WordPress’s built-in drop-in system to provide the most reliable error handling possible. When activated, it:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Installs a Drop-in\u003C\u002Fstrong>: Creates a \u003Ccode>fatal-error-handler.php\u003C\u002Fcode> file in your wp-content directory\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Monitors for Errors\u003C\u002Fstrong>: WordPress automatically uses this drop-in when fatal errors occur\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Captures Error Details\u003C\u002Fstrong>: Records the error message, file, and line number during the shutdown phase\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Identifies the Plugin\u003C\u002Fstrong>: Analyzes the error stack trace to determine which plugin caused the issue\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Deactivates Safely\u003C\u002Fstrong>: Automatically deactivates only the problematic plugin\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Logs Everything\u003C\u002Fstrong>: Stores detailed error information in a permanent log for troubleshooting\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Notifies Admins\u003C\u002Fstrong>: Displays clear admin notices with error details when you next log in\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Shows User-Friendly Pages\u003C\u002Fstrong>: Displays a custom error page with reload button instead of the white screen of death\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>The drop-in approach ensures maximum reliability since it operates at the WordPress core level, even when other plugins fail.\u003C\u002Fp>\n\u003Ch3>Use Cases\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Development Environments\u003C\u002Fstrong>: Test new plugins without worrying about site crashes\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Production Sites\u003C\u002Fstrong>: Add an extra layer of protection against unexpected plugin conflicts\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Managed WordPress\u003C\u002Fstrong>: Essential tool for agencies and freelancers managing multiple client sites\u003C\u002Fli>\n\u003Cli>\u003Cstrong>WooCommerce Stores\u003C\u002Fstrong>: Prevent revenue loss from site downtime due to plugin errors\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Why You Need This Plugin\u003C\u002Fh3>\n\u003Cp>WordPress fatal errors can make your entire site inaccessible, requiring FTP or hosting panel access to fix. With Fatal Plugin Auto Deactivator, your site remains operational even when a plugin causes a critical error, giving you time to address the issue without emergency measures.\u003C\u002Fp>\n","Automatically deactivates plugins that cause fatal errors to prevent site crashes and keep your WordPress site running smoothly.",50,764,"2025-06-01T03:28:00.000Z","5.3","7.0",[66,67,20,68,69],"crash-prevention","error-handling","plugin-deactivation","site-protection","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Ffatal-plugin-auto-deactivator\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffatal-plugin-auto-deactivator.1.1.0.zip",{"slug":73,"name":74,"version":75,"author":76,"author_profile":77,"description":78,"short_description":79,"active_installs":60,"downloaded":80,"rating":25,"num_ratings":25,"last_updated":81,"tested_up_to":46,"requires_at_least":82,"requires_php":18,"tags":83,"homepage":88,"download_link":89,"security_score":13,"vuln_count":25,"unpatched_count":25,"last_vuln_date":26,"fetched_at":27},"wonderful-webhook-alerts","Wonderful Webhook Alerts","1.0.0","wonderfulplugins","https:\u002F\u002Fprofiles.wordpress.org\u002Fwonderfulplugins\u002F","\u003Cp>This plugin provides a simple but powerful function for developers and site administrators. It automatically captures critical PHP errors (fatal errors, parse errors, etc.) that would otherwise take your site down silently.\u003C\u002Fp>\n\u003Cp>Instead of having to check server logs, you receive an instant notification via a webhook to a service of your choice, like \u003Cstrong>Slack\u003C\u002Fstrong> or \u003Cstrong>Discord\u003C\u002Fstrong>. This allows for immediate action and faster debugging.\u003C\u002Fp>\n\u003Cp>The setup is minimal: just add your webhook URL on the settings page, and the plugin takes care of the rest.\u003C\u002Fp>\n","Get real-time notifications for PHP fatal errors sent to your webhook (Slack, Discord, etc.). Never miss a critical site issue again.",347,"2025-12-03T08:34:00.000Z","6.2",[84,20,85,86,87],"debug","monitoring","notification","webhook","https:\u002F\u002Fwonderfulplugins.eu\u002Fwonderful-webhook-alerts","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwonderful-webhook-alerts.1.0.0.zip",{"slug":91,"name":92,"version":93,"author":94,"author_profile":95,"description":96,"short_description":97,"active_installs":25,"downloaded":98,"rating":25,"num_ratings":25,"last_updated":99,"tested_up_to":46,"requires_at_least":63,"requires_php":100,"tags":101,"homepage":105,"download_link":106,"security_score":13,"vuln_count":25,"unpatched_count":25,"last_vuln_date":26,"fetched_at":27},"fatal-to-telegram","Fatal message to Telegram","1.5.1","Phil","https:\u002F\u002Fprofiles.wordpress.org\u002Fphilstudio\u002F","\u003Cp>Fatal message to Telegram monitors your WordPress site for fatal PHP errors and instantly sends detailed crash reports to your Telegram chat.\u003C\u002Fp>\n\u003Cp>Built for developers and sysadmins, this plugin provides early crash detection using a custom MU-plugin loader to hook into PHP before other plugins are even initialized.\u003C\u002Fp>\n\u003Ch3>Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>📡 Sends fatal PHP errors (E_ERROR, E_PARSE, etc.) directly to Telegram\u003C\u002Fli>\n\u003Cli>⚙️ Configurable via WordPress admin (Tools > Fatal message to Telegram)\u003C\u002Fli>\n\u003Cli>🧱 Loads early using a mu-plugin for maximum reliability\u003C\u002Fli>\n\u003Cli>🔐 Automatically installs\u002Fremoves the loader during plugin activation\u002Fremove\u003C\u002Fli>\n\u003Cli>💬 Includes developer-friendly helper functions for manual debugging\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Helper Functions\u003C\u002Fh3>\n\u003Cp>Sends a plain string message to your configured Telegram chat.\u003Cbr \u002F>\n_fttg(“Just a test string”);\u003C\u002Fp>\n\u003Cp>Sends each key-value pair of an array as a separate Telegram message.\u003Cbr \u002F>\n_fttg_array([‘a’ => 1, ‘b’ => 2, ‘c’ => ‘hello’]);\u003C\u002Fp>\n\u003Ch3>External services\u003C\u002Fh3>\n\u003Cp>This plugin connects to the following external services:\u003C\u002Fp>\n\u003Ch3>Telegram Bot API\u003C\u002Fh3>\n\u003Cp>Used to send login alert messages to your Telegram bot\u002Fchat.\u003Cbr \u002F>\n🔗 \u003Ca href=\"https:\u002F\u002Fcore.telegram.org\u002Fbots\u002Fapi\" rel=\"nofollow ugc\">Telegram API Docs\u003C\u002Fa>\u003Cbr \u002F>\n📜 \u003Ca href=\"https:\u002F\u002Ftelegram.org\u002Fprivacy\" rel=\"nofollow ugc\">Telegram Privacy Policy\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>Data sent: Chat ID, bot token (from your settings), and message with IP\u002Flocation\u002Fuser agent info.\u003Cbr \u002F>\nData is only sent when someone logs in and notifications are enabled.\u003Cbr \u002F>\nAll data is not stored locally exclude Chat ID, bot token from your settings.\u003C\u002Fp>\n","Sends fatal PHP errors to Telegram using an early MU-plugin loader. Ideal for monitoring production crashes.",520,"2026-03-14T07:14:00.000Z","7.2",[102,84,103,20,104],"crash-report","error-handler","telegram","https:\u002F\u002Fiphil.top\u002Fportfolio\u002Ffatal-to-telegram\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffatal-to-telegram.1.5.1.zip",{"slug":108,"name":109,"version":110,"author":111,"author_profile":112,"description":113,"short_description":114,"active_installs":25,"downloaded":115,"rating":25,"num_ratings":25,"last_updated":116,"tested_up_to":46,"requires_at_least":117,"requires_php":100,"tags":118,"homepage":122,"download_link":123,"security_score":13,"vuln_count":25,"unpatched_count":25,"last_vuln_date":26,"fetched_at":27},"safe-activate","Safe Activate","1.0.1","Suman Biswas","https:\u002F\u002Fprofiles.wordpress.org\u002Fsumanbiswas013\u002F","\u003Cp>Safe Activate protects your WordPress site from plugin activation failures.\u003C\u002Fp>\n\u003Cp>When a plugin causes a fatal error during activation, Safe Activate automatically:\u003Cbr \u002F>\n* Detects the error\u003Cbr \u002F>\n* Deactivates the problematic plugin\u003Cbr \u002F>\n* Restores admin access\u003Cbr \u002F>\n* Logs the incident for review\u003C\u002Fp>\n\u003Cp>This helps prevent white screen errors and saves time troubleshooting plugin conflicts.\u003C\u002Fp>\n\u003Ch3>Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Automatic detection of fatal plugin errors\u003C\u002Fli>\n\u003Cli>Safe auto-deactivation of conflicting plugins\u003C\u002Fli>\n\u003Cli>Conflict activity logging\u003C\u002Fli>\n\u003Cli>Simple and lightweight\u003C\u002Fli>\n\u003Cli>No configuration required\u003C\u002Fli>\n\u003C\u002Ful>\n","Detects fatal errors during plugin activation and helps admins identify and safely resolve plugin conflicts without automatic actions.",120,"2026-02-11T16:02:00.000Z","5.5",[20,119,120,121],"plugin-activation","plugin-conflict","site-recovery","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fsafe-activate\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsafe-activate.1.0.1.zip",{"attackSurface":125,"codeSignals":174,"taintFlows":207,"riskAssessment":233,"analyzedAt":242},{"hooks":126,"ajaxHandlers":170,"restRoutes":171,"shortcodes":172,"cronEvents":173,"entryPointCount":25,"unprotectedCount":25},[127,133,136,139,142,148,151,156,159,163,166],{"type":128,"name":129,"callback":130,"file":131,"line":132},"filter","recovery_mode_email","closure","dm-rme-filter.php",29,{"type":128,"name":134,"callback":130,"file":131,"line":135},"recovery_mode_email_rate_limit",42,{"type":128,"name":137,"callback":130,"file":131,"line":138},"wp_mail_from",54,{"type":128,"name":140,"callback":130,"file":131,"line":141},"wp_mail_from_name",66,{"type":143,"name":144,"callback":145,"file":146,"line":147},"action","network_admin_menu","dm_rme_settings_menu","dm-rme-settings.php",41,{"type":143,"name":149,"callback":145,"file":146,"line":150},"admin_menu",45,{"type":143,"name":152,"callback":153,"file":154,"line":155},"plugins_loaded","dm_rme_load_textdomain","dm-rme.php",33,{"type":143,"name":157,"callback":158,"file":154,"line":135},"init","dm_rme_deactivate_plugin",{"type":143,"name":160,"callback":161,"file":154,"line":162},"admin_notices","dm_rme_error_notice",68,{"type":143,"name":164,"callback":161,"file":154,"line":165},"network_admin_notices",69,{"type":143,"name":167,"callback":168,"file":154,"line":169},"admin_enqueue_scripts","dm_rme_admin_style",70,[],[],[],[],{"dangerousFunctions":175,"sqlUsage":176,"outputEscaping":182,"fileOperations":25,"externalRequests":25,"nonceChecks":14,"capabilityChecks":205,"bundledLibraries":206},[],{"prepared":25,"raw":14,"locations":177},[178],{"file":179,"line":180,"context":181},"uninstall.php",15,"$wpdb->get_results() with variable interpolation",{"escaped":183,"rawEcho":184,"locations":185},9,10,[186,189,191,193,194,196,198,200,202,203],{"file":146,"line":187,"context":188},78,"raw output",{"file":146,"line":190,"context":188},82,{"file":146,"line":192,"context":188},132,{"file":146,"line":192,"context":188},{"file":146,"line":195,"context":188},133,{"file":146,"line":197,"context":188},149,{"file":146,"line":199,"context":188},166,{"file":146,"line":201,"context":188},172,{"file":146,"line":201,"context":188},{"file":146,"line":204,"context":188},173,8,[],[208,225],{"entryPoint":209,"graph":210,"unsanitizedCount":25,"severity":224},"dm_rme_settings_page (dm-rme-settings.php:52)",{"nodes":211,"edges":221},[212,216],{"id":213,"type":214,"label":215,"file":146,"line":192},"n0","source","$_SERVER['HTTP_HOST'] (x4)",{"id":217,"type":218,"label":219,"file":146,"line":192,"wp_function":220},"n1","sink","echo() [XSS]","echo",[222],{"from":213,"to":217,"sanitized":223},true,"low",{"entryPoint":226,"graph":227,"unsanitizedCount":25,"severity":224},"\u003Cdm-rme-settings> (dm-rme-settings.php:0)",{"nodes":228,"edges":231},[229,230],{"id":213,"type":214,"label":215,"file":146,"line":192},{"id":217,"type":218,"label":219,"file":146,"line":192,"wp_function":220},[232],{"from":213,"to":217,"sanitized":223},{"summary":234,"deductions":235},"The custom-recovery-mode-email plugin v1.0.6 presents a generally good security posture based on the provided static analysis. There are no identified AJAX handlers, REST API routes, shortcodes, or cron events, resulting in zero identified attack surface points and no unprotected entry points. The absence of dangerous functions and external HTTP requests further contributes to a positive security outlook. The plugin also demonstrates a commitment to security by including nonce checks and capability checks, indicating an effort to protect against common WordPress vulnerabilities.",[236,239],{"reason":237,"points":238},"SQL queries not using prepared statements",5,{"reason":240,"points":241},"Significant portion of output not properly escaped",6,"2026-03-16T21:19:57.269Z",{"wat":244,"direct":249},{"assetPaths":245,"generatorPatterns":246,"scriptPaths":247,"versionParams":248},[],[],[],[],{"cssClasses":250,"htmlComments":252,"htmlAttributes":253,"restEndpoints":254,"jsGlobals":255,"shortcodeOutput":256},[251],"dm-rme-error-notice",[],[],[],[],[]]