[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fHJ3AbY5__G_2ns3rcdehzH3UgwEIF2Mu39pa3U-JpP0":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":18,"download_link":25,"security_score":26,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29,"vulnerabilities":30,"developer":31,"crawl_stats":28,"alternatives":38,"analysis":133,"fingerprints":186},"svn-auto-upgrade","SVN Auto Upgrade","1.2","Modern Tribe, Inc.","https:\u002F\u002Fprofiles.wordpress.org\u002Fmoderntribe\u002F","\u003Cp>Description: Hook into plugin and core upgrader to support SVN driven sites. Now you can freely use the WordPress auto upgrade features without worrying about the Subversion impact. Just upgrade in WordPress and then commit the changes in SVN.\u003C\u002Fp>\n\u003Cp>Additionally, this plugin displays the current SVN version in the footer of your admin panel and uses the SVN version to append to your CSS and Javascript embeds so that every time you update from SVN, your media files are cleared form cache.\u003C\u002Fp>\n\u003Cp>Requires that your system permissions allow shell_exec() to execute svn commands.\u003C\u002Fp>\n\u003Cp>Donate – if this is generating enough revenue to support our time it makes all the difference in the world\u003Cbr \u002F>\nhttps:\u002F\u002Fwww.paypal.com\u002Fcgi-bin\u002Fwebscr?cmd=_s-xclick&hosted_button_id=7GVFAADMQ96WA\u003C\u002Fp>\n\u003Ch4>To Do\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Account for SVN externals\u003C\u002Fli>\n\u003Cli>Test to ensure the plugin is compatible with your server (that you can run exec svn commands)\u003C\u002Fli>\n\u003Cli>Build an auto commit option? Not sure if this is a good idea.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Documentation\u003C\u002Fh3>\n\u003Cp>It’s pretty straight forward. When you auto upgrade a plugin or the core, this plugin automatically svn adds and removes files appropriately. That way you can keep your entire WordPress install in SVN.\u003C\u002Fp>\n","Description: Hook into plugin and core upgrader to support SVN driven sites. Now you can freely use the WordPress auto upgrade features without worryi …",10,3025,100,2,"2012-02-26T13:39:00.000Z","3.3.2","3.0","",[20,21,22,23,24],"autoupdate","subversion","svn","update","upgrade","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsvn-auto-upgrade.1.2.zip",85,0,null,"2026-03-15T15:16:48.613Z",[],{"slug":32,"display_name":7,"profile_url":8,"plugin_count":33,"total_installs":34,"avg_security_score":26,"avg_patch_time_days":35,"trust_score":36,"computed_at":37},"moderntribe",7,7830,30,84,"2026-04-04T16:02:52.857Z",[39,59,78,98,116],{"slug":40,"name":41,"version":42,"author":43,"author_profile":44,"description":45,"short_description":46,"active_installs":47,"downloaded":48,"rating":49,"num_ratings":50,"last_updated":51,"tested_up_to":52,"requires_at_least":53,"requires_php":18,"tags":54,"homepage":57,"download_link":58,"security_score":26,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"easy-theme-and-plugin-upgrades","Easy Theme and Plugin Upgrades","2.0.2","Chris Jean","https:\u002F\u002Fprofiles.wordpress.org\u002Fchrisjean\u002F","\u003Cp>WordPress has a built-in feature to install themes and plugins by supplying a zip file. Unfortunately, you cannot upgrade a theme or plugin using the same process. Instead, WordPress will say “destination already exists” when trying to upgrade using a zip file and will fail to upgrade the theme or plugin.\u003C\u002Fp>\n\u003Cp>Easy Theme and Plugin Upgrades fixes this limitation in WordPress by automatically upgrading the theme or plugin if it already exists.\u003C\u002Fp>\n\u003Cp>While upgrading, a backup copy of the old theme or plugin is first created. This allows you to install the old version in case of problems with the new version.\u003C\u002Fp>\n\u003Cp>Attention: Version 2.0.0 changed the functionality of the plugin. You are no longer required to select “Yes” from a drop down before the theme or plugin can be upgraded. The need for an upgrade is now detected automatically. So, if you are used to the old functionality of the plugin, do not be concerned about the absence of upgrade details on the theme and plugin upload pages. Simply upload the theme or plugin as if you were installing it, and the plugin will automatically handle upgrading as needed.\u003C\u002Fp>\n","Easily upgrade your themes and plugins using zip files without removing the theme or plugin first.",70000,1436562,94,117,"2022-04-20T03:40:00.000Z","5.7.15","4.4",[55,23,24,56],"theme","upload","http:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Feasy-theme-and-plugin-upgrades\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Feasy-theme-and-plugin-upgrades.2.0.2.zip",{"slug":60,"name":61,"version":62,"author":63,"author_profile":64,"description":65,"short_description":66,"active_installs":67,"downloaded":68,"rating":13,"num_ratings":69,"last_updated":70,"tested_up_to":52,"requires_at_least":71,"requires_php":72,"tags":73,"homepage":18,"download_link":77,"security_score":26,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"ajax-cart-autoupdate-for-woocommerce","Ajax Cart AutoUpdate for WooCommerce","1.5.5","taisho","https:\u002F\u002Fprofiles.wordpress.org\u002Ftaisho\u002F","\u003Cp>A light plugin that automatically updates cart page and mini-cart when product quantity is changed. Removes the default “Update cart” button. Optionally turns off cart page notices.\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Cart page and mini-cart widget are updated automatically on quantity change through Ajax (no page reloading).\u003C\u002Fli>\n\u003Cli>“Update cart” button is removed from the cart page.\u003C\u002Fli>\n\u003Cli>Both mouse and keyboard changes are supported.\u003C\u002Fli>\n\u003Cli>Works for custom dropdown lists with ‘qty’ class.\u003C\u002Fli>\n\u003Cli>Compatible with plugin \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fqty-increment-buttons-for-woocommerce\u002F\" rel=\"ugc\">Qty Increment Buttons for WooCommerce\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>Uses the default WooCommerce cart update event.\u003C\u002Fli>\n\u003Cli>Cart update is delayed by time in milliseconds since the last action affecting quantity, changeable in plugin settings, default 1000. It means that the update will fire only once when the customer is done with changes.\u003C\u002Fli>\n\u003Cli>Optionally change min quantity in the cart from 0 to 1, on by default.\u003C\u002Fli>\n\u003Cli>Optionally remove all notices from the cart page, on by default.\u003C\u002Fli>\n\u003C\u002Ful>\n","A light plugin that automatically updates cart page and mini-cart when product quantity is changed. Removes the default \"Update cart\" button …",9000,84819,214,"2021-03-30T21:37:00.000Z","4.6","5.4",[74,20,75,23,76],"ajax","cart","woocommerce","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fajax-cart-autoupdate-for-woocommerce.1.5.5.zip",{"slug":79,"name":80,"version":81,"author":82,"author_profile":83,"description":84,"short_description":85,"active_installs":86,"downloaded":87,"rating":13,"num_ratings":88,"last_updated":89,"tested_up_to":90,"requires_at_least":91,"requires_php":92,"tags":93,"homepage":18,"download_link":97,"security_score":26,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"disable-plugin-autoupdate-emails","Disable Plugin Autoupdate Emails","1.1.3","simshaun","https:\u002F\u002Fprofiles.wordpress.org\u002Fsimshaun\u002F","\u003Cp>There’s not much to this plugin. It’s a couple barebones filters that turn off the plugin and theme autoupdate emails.\u003C\u002Fp>\n\u003Cp>On WordPress 5.5.0, plugin\u002Ftheme autoupdate emails are turned off regardless of whether or not they failed.\u003C\u002Fp>\n\u003Cp>Since WordPress 5.5.1, emails indicating update failures are allowed through.\u003C\u002Fp>\n","Getting too many \"plugin updated\" or \"theme updated\" emails since WordPress 5.5? This turns them off.",6000,39316,6,"2024-03-22T05:34:00.000Z","6.4.8","5.5","5.3",[94,95,96],"autoupdates","disable-autoupdate-email","updates","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdisable-plugin-autoupdate-emails.zip",{"slug":99,"name":100,"version":101,"author":102,"author_profile":103,"description":104,"short_description":105,"active_installs":106,"downloaded":107,"rating":13,"num_ratings":108,"last_updated":109,"tested_up_to":110,"requires_at_least":111,"requires_php":18,"tags":112,"homepage":18,"download_link":115,"security_score":26,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"simple-automatic-updates","Simple Automatic Updates","0.1.3","Jon Tejnung","https:\u002F\u002Fprofiles.wordpress.org\u002Fxpoon\u002F","\u003Cp>This plugin will give you three alternatives for managing your WordPress updates:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Update automatically\u003C\u002Fstrong> – This updates WordPress\u002Fthemes\u002Fplugins automatically and sends an email to the site admin when an update has been performed.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Update automatically (no email)\u003C\u002Fstrong> – Same as the first alternative, but without the email.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Inform about updates once a week\u003C\u002Fstrong> – This will send an email to the admin once a week if there are anything that can be updated.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Notice that only plugins\u002Fthemes that resides in the WordPress\u003Cbr \u002F>\nrepository will be updated\u002Finformed about.\u003C\u002Fp>\n\u003Cp>The plugin has not been tested and is not primarily made for multi site-installations.\u003C\u002Fp>\n","Activate automatic updates or weekly notifications for the site.",2000,22860,1,"2019-06-11T06:58:00.000Z","5.2.24","4.0",[113,114,23,24],"auto","security","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsimple-automatic-updates.0.1.3.zip",{"slug":117,"name":118,"version":119,"author":120,"author_profile":121,"description":122,"short_description":123,"active_installs":124,"downloaded":125,"rating":13,"num_ratings":126,"last_updated":127,"tested_up_to":128,"requires_at_least":111,"requires_php":18,"tags":129,"homepage":18,"download_link":132,"security_score":26,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"fix-windows-compatibility","Windows Compatibility Fix","1.0.2","Dave Jesch","https:\u002F\u002Fprofiles.wordpress.org\u002Fdavejesch\u002F","\u003Cp>This plugin will fix long filename problems on Windows systems when doing updates from third-party plugin repositories, such as updating from EDD based sites.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Usage Scenarios:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>We’ve found that users on Windows systems that are upgrading themes and plugins from a third-party repository, such as an Easy Digital Downloads (EDD) site have problems. They will see an error message of “Update Failed: Could not create directory…”. The reason for this is that during the update process, the file name requested from the EDD site has the product name, user name and other information encoded within it so that EDD knows who is requesting the file. This results in a very long file name. This is not necessarily a problem WordPress itself, or even EDD, as this works on non-Windows systems. But if you are running WordPress on Windows and see this error, it is because of the long file name requested.\u003C\u002Fp>\n\u003Cp>If you are using DesktopServer for your local development on Windows and would like to use the Windows Compatibility Fix plugin as a Design Time plugin, you can install this in your C:\\xampplite\\ds-plugings directory and it can then be automatically activated and used with all of your local development web sites. This allows you to use the plugin in your local environment, where it’s needed and not to deploy it to your live environment where it may not be needed. For more information on DesktopServer and local development tools, please visit our web site at: https:\u002F\u002Fserverpress.com\u002Fget-desktopserver\u002F\u003C\u002Fp>\n\u003Cp>Because this fix is only needed on Windows systems, the plugin checks the operating system on which it is running and does not initialize itself. If you are having problems with the update process on non-Windows systems, it is more likely an issue with directory permissions.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>How it Works:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>The Windows Compatibility Fix plugin uses a couple of WordPress filters employed during the update process. It modifies the name of the file that is downloaded to your system, shortening it to just a few characters. This allows WordPress’s update process to work correctly on Windows systems by not creating the long file name in the first place.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Support:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>\u003Cstrong>Support Details:\u003C\u002Fstrong> We are happy to provide support and help troubleshoot issues. Visit our Contact page at \u003Ca href=\"http:\u002F\u002Fserverpress.com\u002Fcontact\u002F\" rel=\"nofollow ugc\">http:\u002F\u002Fserverpress.com\u002Fcontact\u002F\u003C\u002Fa>. Users should know however, that we check the WordPress.org support forums once a week on Wednesdays from 6pm to 8pm PST (UTC -8).\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>ServerPress, LLC is not responsible for any loss of data that may occur as a result of using this tool. We strongly recommend performing a site and database backup before testing and using this tool. However, should you experience such an issue, we want to know about it right away.\u003C\u002Fp>\n\u003Cp>We welcome feedback and Pull Requests for this plugin via our public GitHub repository located at: \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FServerPress\u002FWindows-Compatibility-Fix\" rel=\"nofollow ugc\">https:\u002F\u002Fgithub.com\u002FServerPress\u002FWindows-Compatibility-Fix\u003C\u002Fa>\u003C\u002Fp>\n","Fixes long filename problem on Windows systems when doing updates, such as updating from EDD based sites.",1000,17085,8,"2018-10-22T03:07:00.000Z","5.0.25",[130,55,23,24,131],"long-filename","windows","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffix-windows-compatibility.zip",{"attackSurface":134,"codeSignals":163,"taintFlows":178,"riskAssessment":179,"analyzedAt":185},{"hooks":135,"ajaxHandlers":159,"restRoutes":160,"shortcodes":161,"cronEvents":162,"entryPointCount":27,"unprotectedCount":27},[136,142,146,150,155],{"type":137,"name":138,"callback":139,"priority":11,"file":140,"line":141},"filter","upgrader_pre_install","makeSvnBackup","svn-auto-upgrade.php",26,{"type":137,"name":143,"callback":144,"priority":11,"file":140,"line":145},"upgrader_post_install","restoreSvnFolders",27,{"type":137,"name":147,"callback":148,"file":140,"line":149},"admin_footer_text","adminPrintSvnInfo",28,{"type":137,"name":151,"callback":152,"priority":153,"file":140,"line":154},"bloginfo","overwriteVersion",20,29,{"type":156,"name":157,"callback":158,"file":140,"line":35},"action","admin_footer","globalSvnAddRemove",[],[],[],[],{"dangerousFunctions":164,"sqlUsage":172,"outputEscaping":174,"fileOperations":176,"externalRequests":27,"nonceChecks":108,"capabilityChecks":27,"bundledLibraries":177},[165,169],{"fn":166,"file":140,"line":167,"context":168},"shell_exec",123,"shell_exec(\"svn add `svn status $path | grep '^?' | awk '{ print $2 }' | xargs`\");",{"fn":166,"file":140,"line":170,"context":171},124,"shell_exec(\"svn delete --force `svn status $path | grep '^!' | awk '{ print $2 }' | xargs`\");",{"prepared":27,"raw":27,"locations":173},[],{"escaped":14,"rawEcho":27,"locations":175},[],3,[],[],{"summary":180,"deductions":181},"The svn-auto-upgrade v1.2 plugin presents a mixed security posture.  On the positive side, the plugin demonstrates good practices regarding database interaction with 100% prepared statements and proper output escaping.  It also includes a nonce check and avoids external HTTP requests. The absence of any known vulnerabilities or CVEs in its history is a significant strength, suggesting a generally well-maintained codebase.  However, the presence of two instances of the `shell_exec` function is a notable concern. While the static analysis doesn't reveal any immediate exploitable flows due to `shell_exec`, its mere existence introduces a potential attack vector if not meticulously handled or if future versions introduce vulnerabilities in how user input influences its execution. The limited attack surface and lack of direct file operations without any context also contribute positively to its current security. Overall, the plugin's past record is excellent, but the `shell_exec` usage warrants careful monitoring and a thorough review of its implementation to ensure no latent risks exist.",[182],{"reason":183,"points":184},"Use of dangerous function shell_exec",15,"2026-03-17T00:13:56.554Z",{"wat":187,"direct":192},{"assetPaths":188,"generatorPatterns":189,"scriptPaths":190,"versionParams":191},[],[],[],[],{"cssClasses":193,"htmlComments":195,"htmlAttributes":196,"restEndpoints":197,"jsGlobals":198,"shortcodeOutput":199},[194],"svn-info-admin",[],[],[],[],[]]