[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fKo0sDu-_GBSZpzip6HF0if4HuEmq2ghVhmLzCpxKfo4":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":25,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28,"vulnerabilities":29,"developer":30,"crawl_stats":27,"alternatives":38,"analysis":136,"fingerprints":177},"disable-site-delete","Disable Site Delete","1.0","Brajesh Singh","https:\u002F\u002Fprofiles.wordpress.org\u002Fsbrajesh\u002F","\u003Cp>Disable Site Delete plugin only allows network administrators to delete a blog\u002Fsite on a WordPress Multisite network. It does not allow blog owners to delete their blogs.\u003C\u002Fp>\n\u003Cp>It works by doing that in 3 steps:-\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Removes the delete Site link from tools menu for non network admins\u003C\u002Fli>\n\u003Cli>Breaks out of wpmu_delete_blog function to avoid deletion of blog\u003C\u002Fli>\n\u003Cli>hacks around option to avoid sending the delete confirmation mail to blog owner\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Need more details, please visit this post on \u003Ca href=\"http:\u002F\u002Fbuddydev.com\u002Fwordpress-multisite\u002Fintroducing-disable-site-delete-plugin-for-wordpress-multisite-based-networks\u002F\" title=\"Introducing Disable Site Delete plugin\" rel=\"nofollow ugc\">BuddyDev\u003C\u002Fa>\u003C\u002Fp>\n","Disable Site Delete plugin completely disables the site\u002Fblog deletion by a non network administrator",10,2986,100,2,"2015-08-12T19:08:00.000Z","4.2.39","3.0","",[20,21,22],"blog","delete","multisite","http:\u002F\u002Fbuddydev.com\u002Fplugins\u002Fdisable-delete-site\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdisable-site-delete.1.0.zip",85,0,null,"2026-03-15T15:16:48.613Z",[],{"slug":31,"display_name":7,"profile_url":8,"plugin_count":32,"total_installs":33,"avg_security_score":34,"avg_patch_time_days":35,"trust_score":36,"computed_at":37},"sbrajesh",12,1820,86,3856,69,"2026-04-04T11:07:24.518Z",[39,62,82,101,119],{"slug":40,"name":41,"version":42,"author":43,"author_profile":44,"description":45,"short_description":46,"active_installs":47,"downloaded":48,"rating":13,"num_ratings":49,"last_updated":50,"tested_up_to":51,"requires_at_least":52,"requires_php":53,"tags":54,"homepage":18,"download_link":58,"security_score":59,"vuln_count":60,"unpatched_count":26,"last_vuln_date":61,"fetched_at":28},"delete-me","Delete Me","3.2","cmc3215","https:\u002F\u002Fprofiles.wordpress.org\u002Fcmc3215\u002F","\u003Cp>Allow users with specific WordPress roles to delete themselves from the \u003Cstrong>Your Profile\u003C\u002Fstrong> page or anywhere Shortcodes can be used using the Shortcode \u003Ccode>[plugin_delete_me \u002F]\u003C\u002Fcode>.\u003Cbr \u002F>\nSettings for this plugin are found on the \u003Cstrong>Settings -> Delete Me\u003C\u002Fstrong> subpanel. Multisite and Network Activation supported.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>How it works:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>A user clicks the delete link, which defaults to “Delete Account”, but can be changed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>User is asked to confirm they want to delete themselves.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>If confirmed, user and all their Posts, Links, and (optionally) Comments are deleted.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Deleted user (optionally) redirected to landing page URL, default is homepage, can be changed or left blank.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Settings available:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>Enable or disable Network Wide, which applies a single page of settings across all Multisite network Sites.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Select specific WordPress roles (e.g. Subscriber) you want to allow to delete themselves using Delete Me.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ccode>class\u003C\u002Fcode> and \u003Ccode>style\u003C\u002Fcode> attributes of the delete link.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ccode>\u003Ca>\u003C\u002Fcode> tag clickable content of the delete link.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Landing page URL.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Your Profile\u003C\u002Fstrong> confirmation page Heading, Warning, Password (optionally require password), Button.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Enable or disable delete link on the \u003Cstrong>Your Profile\u003C\u002Fstrong> page.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Javascript confirm text for Shortcode.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Enable or disable Javascript confirm for Shortcode.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Enable or disable using a form (require password) instead of a link for Shortcode.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Multisite: Delete user from entire Network or current Site only.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Delete comments.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>E-mail notification when a user deletes themselves.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n","Allow users with specific WordPress roles to delete themselves from the Your Profile page or anywhere Shortcodes can be used.",8000,107894,23,"2024-06-02T14:24:00.000Z","6.5.8","3.7","5.2.4",[21,55,22,56,57],"gdpr","unsubscribe","user-management","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdelete-me.3.2.zip",92,1,"2023-10-23 00:00:00",{"slug":63,"name":64,"version":65,"author":66,"author_profile":67,"description":68,"short_description":69,"active_installs":13,"downloaded":70,"rating":71,"num_ratings":72,"last_updated":73,"tested_up_to":74,"requires_at_least":17,"requires_php":18,"tags":75,"homepage":80,"download_link":81,"security_score":25,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"multisite-cloner","Multisite Cloner","0.2.2.1","Manuel Razzari","https:\u002F\u002Fprofiles.wordpress.org\u002Fmanuelrazzari\u002F","\u003Cp>In WordPress Multisite, new sites get a boring default template, without any custom settings or starter content.\u003C\u002Fp>\n\u003Cp>This plugin allows you to select a specific blog on your network, a “master” one, that will be cloned every time a new blog is created.\u003C\u002Fp>\n\u003Cp>In this way, new blogs will contain all posts, uploads, theme settings and plugin options from the master blog.\u003C\u002Fp>\n\u003Ch4>How does it work?\u003C\u002Fh4>\n\u003Col>\n\u003Cli>It uses MySQL \u003Ccode>INSERT INTO ... SELECT\u003C\u002Fcode> to copy \u003Cem>every\u003C\u002Fem> table from the “master” blog into the new one. This is fast!\u003C\u002Fli>\n\u003Cli>Then it does a search and replace on the new blog’s tables, to replace the old URL with the new one.\u003Cbr \u002F>\nThis is done in a way that respects serialized arrays, so your plugin’s settings will be preserved.\u003Cbr \u002F>\n(We used a heavily trimmed down version of Interconnect\u002FIT’s \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Finterconnectit\u002FSearch-Replace-DB\" rel=\"nofollow ugc\">Search and Replace\u003C\u002Fa> tool for that, so go thank them for this!)\u003C\u002Fli>\n\u003Cli>It proceeds to copy all files from the \u003Ccode>wp-content\u002Fuploads\u003C\u002Fcode> dir of your master blog into the new one’s, so that all assets will work as expected.\u003C\u002Fli>\n\u003Cli>Finally it does some house clean-up, updating the new blog’s title, admin email, and user roles as needed.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Go check the screenshots, it’s really simple and does what it says.\u003Cbr \u002F>\nGive it a try!\u003C\u002Fp>\n\u003Cp>\u003Cem>This plugin was handcrafted with love and ‘yerba mate’ by the team at \u003Ca href=\"http:\u002F\u002Fwww.tipit.net\u002F\" title=\"Sustainable Web development since 1996 in Austin, Texas\" rel=\"nofollow ugc\">Tipit.net\u003C\u002Fa>.\u003C\u002Fem>\u003C\u002Fp>\n","When creating a new blog on WordPress Multisite, copies all the posts, settings and files, from a selected blog into the new one.",35036,94,29,"2016-11-18T20:45:00.000Z","4.6.30",[76,77,78,22,79],"clone","copy","copy-blog","wpmu","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fmultisite-cloner","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fmultisite-cloner.zip",{"slug":83,"name":84,"version":85,"author":86,"author_profile":87,"description":88,"short_description":89,"active_installs":90,"downloaded":91,"rating":13,"num_ratings":14,"last_updated":92,"tested_up_to":93,"requires_at_least":94,"requires_php":18,"tags":95,"homepage":99,"download_link":100,"security_score":25,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"wp-over-network","WP Over Network","0.4.4","yuka2py","https:\u002F\u002Fprofiles.wordpress.org\u002Fyuka2py\u002F","\u003Cp>Add ability to get posts from over your network sites. Supports widget, shortcode, and customizable original function.\u003C\u002Fp>\n\u003Cp>Use the following:\u003C\u002Fp>\n\u003Ch4>In template\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>\u003C?php \n\nget_header();\nthe_post();\n\n?>\n\u003Csection id=\"content-primary\">\n        \u003Cheader id=\"page-header\">\n                \u003Ch1>\u003C?php the_title() ?>\u003C\u002Fh1>\n        \u003C\u002Fheader>\n\u003C?php\n\n\u002F\u002F Getting recent posts the page and post, minus the host blog.\n\u002F\u002F Specify the \"affect_wp_query = true\", for using the wp_pagenavi.\n$posts = wponw::get_posts('exclude_blog_ids=1&post_type=post,page&affect_wp_query=true');\n\nwp_pagenavi();\n\n?>\n\u003C?php if ( ! empty ( $posts ) ) : ?>\n        \u003Csection class=\"post-list\">\n\u003C?php\n        foreach ( $posts as $post ) :\n                wponw::setup_blog_and_postdata( $post );\n?>\n                \u003Csection id=\"post-\u003C?php the_ID() ?>\" \u003C?php post_class() ?>>\n                        \u003Ch2>【\u003C?php echo $post->blog_name ?>】\u003C\u002Fh2>\n                        \u003Ch1>\u003Ca href=\"\u003C?php the_permalink() ?>\">\u003C?php the_title() ?>\u003C\u002Fa>\u003C\u002Fh1>\n                        \u003C?php echo get_the_excerpt() ?>\n                \u003C\u002Fsection>\n\u003C?php\n                wponw::restore_blog_and_postdata();\n        endforeach;\n?>\n        \u003C\u002Fsection>\n\u003C?php else : ?>\n        \u003Cp>Sorry, there is no post.\u003C\u002Fp>\n\u003C?php endif; # End of empty( $posts ) ?>\n\n\u003C\u002Fsection>\n\u003C?php\n\nwp_reset_query();\nget_sidebar();\nget_footer();\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Using as Shortcode\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>Display with default.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[wponw_recent_post_list]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Arguments, can be used the same as \u003Ccode>wponw::render_post_archive_to_string\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Use your template file, includes 3 post types\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[wponw_recent_post_list numberposts=8 post_type=products,promotions,information template=TemplateFileNameInYourTheme]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>NOTICE: DON’T include the file extension in TemplateFileNameInYourTheme.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>If you want to use your own rendering function.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[wponw_recent_post_list numberposts=5 post_type=products renderer=YourRenderFunction]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>To create an archive page with a page.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>You create the new page, and write the below shortcode in the post content.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[wponw_recent_post_list post_type=post exclude_blog_ids=1 affect_wp_query=true]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3>Contact\u003C\u002Fh3>\n\u003Cp>@yuka2py on twitter\u003C\u002Fp>\n","Add ability to get posts from over your network sites. Supports widget, shortcode, and customizable original function.",90,6272,"2013-07-28T02:40:00.000Z","3.5.2","3.5",[96,22,97,98],"blogs","network","posts","https:\u002F\u002Fgithub.com\u002Fyuka2py\u002Fwp_over_network","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-over-network.0.4.4.zip",{"slug":102,"name":103,"version":104,"author":105,"author_profile":106,"description":107,"short_description":108,"active_installs":109,"downloaded":110,"rating":13,"num_ratings":14,"last_updated":111,"tested_up_to":112,"requires_at_least":17,"requires_php":18,"tags":113,"homepage":117,"download_link":118,"security_score":25,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"style-stripper","Style Stripper","1.0.1","ericjuden","https:\u002F\u002Fprofiles.wordpress.org\u002Fericjuden\u002F","\u003Cp>Removes all inline style tags from the content of posts\u002Fpages\u002Fcustom post types.\u003C\u002Fp>\n","Removes all inline style tags from the content of posts\u002Fpages\u002Fcustom post types.",80,3817,"2016-05-17T17:46:00.000Z","4.5.33",[21,114,22,115,116],"inline-styles","remove","styles","http:\u002F\u002Fjudenware.com\u002Fprojects\u002Fwordpress\u002Fstyle-stripper\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fstyle-stripper.zip",{"slug":120,"name":121,"version":122,"author":105,"author_profile":106,"description":123,"short_description":124,"active_installs":125,"downloaded":126,"rating":13,"num_ratings":127,"last_updated":128,"tested_up_to":129,"requires_at_least":130,"requires_php":18,"tags":131,"homepage":134,"download_link":135,"security_score":25,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"reorder-my-sites","Reorder My Sites","1.2","\u003Cp>For WordPress Multisite. Reorders the My Sites dropdown menu in the Admin Bar alphabetically. It keeps the main blog at the top.\u003C\u002Fp>\n","For WordPress Multisite. Reorders the My Sites dropdown menu in the Admin Bar alphabetically. It keeps the main blog at the top.",40,4012,6,"2018-05-09T03:30:00.000Z","4.9.29","3.3",[96,22,132,133,79],"my-sites","sites","http:\u002F\u002Fjudenware.com\u002Fprojects\u002Fwordpress\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Freorder-my-sites.zip",{"attackSurface":137,"codeSignals":161,"taintFlows":168,"riskAssessment":169,"analyzedAt":176},{"hooks":138,"ajaxHandlers":157,"restRoutes":158,"shortcodes":159,"cronEvents":160,"entryPointCount":26,"unprotectedCount":26},[139,145,149,153],{"type":140,"name":141,"callback":142,"file":143,"line":144},"action","admin_menu","remove_delete_from_menu","disable-site-delete.php",25,{"type":140,"name":146,"callback":147,"priority":11,"file":143,"line":148},"delete_blog","disable_delete_cap",27,{"type":140,"name":150,"callback":151,"priority":11,"file":143,"line":152},"pre_update_option_delete_blog_hash","disable_delete_option",30,{"type":140,"name":154,"callback":155,"file":143,"line":156},"plugins_loaded","load_localization",32,[],[],[],[],{"dangerousFunctions":162,"sqlUsage":163,"outputEscaping":165,"fileOperations":26,"externalRequests":26,"nonceChecks":26,"capabilityChecks":26,"bundledLibraries":167},[],{"prepared":26,"raw":26,"locations":164},[],{"escaped":26,"rawEcho":26,"locations":166},[],[],[],{"summary":170,"deductions":171},"The 'disable-site-delete' plugin version 1.0 exhibits a strong security posture based on the provided static analysis.  The plugin has zero identified entry points, meaning it does not expose any AJAX handlers, REST API routes, shortcodes, or cron events that could be directly exploited by an attacker. Furthermore, the code analysis reveals no dangerous function usage, all SQL queries are prepared, and all outputs are properly escaped. The absence of file operations and external HTTP requests further minimizes the attack surface. The plugin's vulnerability history is also clean, with no recorded CVEs, indicating a history of secure development or minimal public exposure to attacks.\n\nWhile the current analysis shows no immediate risks, a critical weakness is the complete lack of capability checks and nonce checks. This indicates that even if an attacker were to find an indirect way to trigger functionality within the plugin, there are no built-in protections to verify if the user initiating the action has the necessary permissions or if the request is legitimate. The absence of these checks, while not currently exploitable due to the zero attack surface, represents a significant potential vulnerability if the plugin's functionality were ever to be extended or accessed through an unforeseen vector.\n\nIn conclusion, 'disable-site-delete' v1.0 is exceptionally secure in its current implementation, demonstrating excellent development practices by avoiding common pitfalls. However, the complete omission of capability and nonce checks is a notable concern that could become a critical weakness if the plugin's attack surface ever expands. The perfect vulnerability history is a positive indicator, but it should not be relied upon solely as a guarantee of future security.",[172,174],{"reason":173,"points":11},"No capability checks",{"reason":175,"points":11},"No nonce checks","2026-03-17T00:25:02.049Z",{"wat":178,"direct":183},{"assetPaths":179,"generatorPatterns":180,"scriptPaths":181,"versionParams":182},[],[],[],[],{"cssClasses":184,"htmlComments":185,"htmlAttributes":186,"restEndpoints":187,"jsGlobals":188,"shortcodeOutput":189},[],[],[],[],[],[]]