[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fLNocMNvgeDhQJji1kGrcAN2yDbxgOzHepLHlkcY9KJw":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":19,"download_link":20,"security_score":21,"vuln_count":13,"unpatched_count":13,"last_vuln_date":22,"fetched_at":23,"vulnerabilities":24,"developer":25,"crawl_stats":22,"alternatives":33,"analysis":34,"fingerprints":60},"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,0,"2025-12-05T08:48:00.000Z","6.9.4","4.6","5.6",[4],"https:\u002F\u002Fjosemortellaro.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdisable-fatal-error-handler.0.0.4.zip",100,null,"2026-03-15T15:16:48.613Z",[],{"slug":26,"display_name":7,"profile_url":8,"plugin_count":27,"total_installs":28,"avg_security_score":29,"avg_patch_time_days":30,"trust_score":31,"computed_at":32},"giuse",56,26370,99,62,87,"2026-04-04T02:41:17.905Z",[],{"attackSurface":35,"codeSignals":41,"taintFlows":49,"riskAssessment":50,"analyzedAt":59},{"hooks":36,"ajaxHandlers":37,"restRoutes":38,"shortcodes":39,"cronEvents":40,"entryPointCount":13,"unprotectedCount":13},[],[],[],[],[],{"dangerousFunctions":42,"sqlUsage":43,"outputEscaping":45,"fileOperations":47,"externalRequests":13,"nonceChecks":13,"capabilityChecks":13,"bundledLibraries":48},[],{"prepared":13,"raw":13,"locations":44},[],{"escaped":13,"rawEcho":13,"locations":46},[],2,[],[],{"summary":51,"deductions":52},"The \"disable-fatal-error-handler\" plugin v0.0.4 presents a generally positive security posture based on the provided static analysis and vulnerability history. The plugin exhibits excellent security practices, with no identified dangerous functions, all SQL queries using prepared statements, and all output being properly escaped. Furthermore, there are no known vulnerabilities (CVEs) associated with this plugin, indicating a clean history and proactive security.\n\nHowever, the analysis does highlight a few areas that, while not immediately critical, warrant attention. The presence of file operations without any apparent capability checks or nonce validation raises a potential concern. If these file operations are exposed in a way that can be triggered by unauthenticated users, they could represent an attack vector. The lack of any identified entry points in the static analysis is also unusual, and it's worth verifying that no subtle or indirect entry points have been missed.\n\nIn conclusion, the plugin's foundation is strong, characterized by secure coding practices and a lack of historical vulnerabilities. The primary area for improvement lies in clarifying and securing the identified file operations to ensure they are not exploitable. Addressing these points would further strengthen its security profile.",[53,56],{"reason":54,"points":55},"File operations without capability checks",10,{"reason":57,"points":58},"File operations without nonce checks",8,"2026-03-16T20:12:02.921Z",{"wat":61,"direct":66},{"assetPaths":62,"generatorPatterns":63,"scriptPaths":64,"versionParams":65},[],[],[],[],{"cssClasses":67,"htmlComments":68,"htmlAttributes":69,"restEndpoints":70,"jsGlobals":71,"shortcodeOutput":72},[],[],[],[],[],[]]