[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fiZ2WYX2OHUp7tcIzwARIsvOXA-gjWKabADwqdJ1YK5Y":3,"$fCwADkDuS8zsCRAHUpP-443-eD0Rge4i0cmPSfedVPwY":187,"$f4NA3xLkMD5W_jutRCmfdfcHOgXzCdt35vNQFY5-p26w":192},{"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":25,"download_link":26,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30,"discovery_status":31,"vulnerabilities":32,"developer":33,"crawl_stats":29,"alternatives":40,"analysis":150,"fingerprints":174},"redirect-multisite-user-to-their-own-site","Redirect multisite user to their own site (UNMAINTAINED)","1.1.2","Mark Howells-Mead","https:\u002F\u002Fprofiles.wordpress.org\u002Fmarkhowellsmead\u002F","\u003Cp>\u003Cstrong>THIS PLUGIN IS NO LONGER MAINTAINED.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>If the current user in a multisite environment accesses a subsite to which access has not been granted, then redirect the user back to their own site. If the user has been granted access to more than one site in the Multisite installation, then no redirect can occur. (Because there is no way of finding out which one is “correct”.)\u003C\u002Fp>\n\u003Ch3>Information for developers\u003C\u002Fh3>\n\u003Cp>There are three action hooks available to developers. You can use them, for example, to write a log file or notify an email address when an action is carried out.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>redirect-multisite-user-to-their-own-site\u002Fno-sites\u003C\u002Fcode> fires when the user is logged in but does not have specific access to any sites in the current Multisite installation. Receives the values \u003Ccode>$current_user\u003C\u002Fcode> (WordPress User object) and \u003Ccode>$current_site_id\u003C\u002Fcode> (integer) as attributes.\u003C\u002Fli>\n\u003Cli>\u003Ccode>redirect-multisite-user-to-their-own-site\u002Fredirecting\u003C\u002Fcode> fires immediately before the user is redirected to the appropriate site. Receives the values \u003Ccode>$current_user\u003C\u002Fcode> (WordPress User object), \u003Ccode>$current_site_id\u003C\u002Fcode> (integer) and \u003Ccode>$user_target_site->siteurl\u003C\u002Fcode> (the URL to which the user will be redirected) as attributes.\u003C\u002Fli>\n\u003Cli>\u003Ccode>redirect-multisite-user-to-their-own-site\u002Fnot-allowed\u003C\u002Fcode> fires when the user has authorized access to more than one site in the installation, and can therefore not be redirected. Receives the values \u003Ccode>$current_user\u003C\u002Fcode> (WordPress User object), \u003Ccode>$current_site_id\u003C\u002Fcode> (integer) and \u003Ccode>$user_sites\u003C\u002Fcode> (array) as attributes.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This plugin requires PHP 5.3 or newer because it uses PHP namespaces.\u003C\u002Fp>\n","Redirect a multisite user to their own site.",10,2628,100,1,"2022-11-11T16:31:00.000Z","4.6.30","4.5","",[20,21,22,23,24],"multisite","parse_request","redirect","user","wpmu","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fredirect-multisite-user-to-their-own-site\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fredirect-multisite-user-to-their-own-site.zip",85,0,null,"2026-04-16T10:56:18.058Z","no_bundle",[],{"slug":34,"display_name":7,"profile_url":8,"plugin_count":11,"total_installs":35,"avg_security_score":36,"avg_patch_time_days":37,"trust_score":38,"computed_at":39},"markhowellsmead",1570,96,30,91,"2026-05-20T01:27:14.924Z",[41,61,83,104,127],{"slug":42,"name":43,"version":44,"author":45,"author_profile":46,"description":47,"short_description":48,"active_installs":49,"downloaded":50,"rating":13,"num_ratings":51,"last_updated":52,"tested_up_to":53,"requires_at_least":54,"requires_php":18,"tags":55,"homepage":59,"download_link":60,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"multisite-user-role-manager","Multisite User Role Manager","1.0.7","OzTheGreat","https:\u002F\u002Fprofiles.wordpress.org\u002Fozthegreat\u002F","\u003Cp>For WordPress Multisite (WPMU) installs, allows Super Admins to easily manage each users roles and blogs from one\u003Cbr \u002F>\nscreen in the Network Admin menu.\u003C\u002Fp>\n\u003Cp>You no longer have to go to each blog to change the user’s role. It’s also\u003Cbr \u002F>\nmuch easier to see which sites a user is associated with.\u003C\u002Fp>\n","Manage user roles for each blog from a single screen on multisite (WPMU) setups",80,30365,3,"2017-11-07T14:04:00.000Z","4.8.28","4.0",[56,20,57,58,24],"management","roles","users","https:\u002F\u002Fwpartisan.me\u002Fplugins\u002Fmultisite-user-role-manager","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fmultisite-user-role-manager.1.0.7.zip",{"slug":62,"name":63,"version":64,"author":65,"author_profile":66,"description":67,"short_description":68,"active_installs":11,"downloaded":69,"rating":70,"num_ratings":71,"last_updated":72,"tested_up_to":73,"requires_at_least":74,"requires_php":75,"tags":76,"homepage":80,"download_link":81,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":82},"wpmu-plugin-stats","WPMU Plugin Stats","3.0.1","DeannaS","https:\u002F\u002Fprofiles.wordpress.org\u002Fdeannas\u002F","\u003Cblockquote>\n\u003Cp>The plugin is deprecated and reaches a hard end-of-life date on 31. January 2018!\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch4>Alternative\u003C\u002Fh4>\n\u003Cp>You should switch to \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fmultisite-enhancements\u002F\" rel=\"ugc\">Multisite Enhancements\u003C\u002Fa>. It provides the same functionality and is actively maintained.\u003C\u002Fp>\n\u003Cp>This plugin gives you a count and the listing of sites using your installed plugins.\u003C\u002Fp>\n\u003Cp>Usage data is cached in a Transient (non-autoloading) but the data collection process can be a very expensive operation depending on plugin and (especially) site count.\u003Cbr \u002F>\nCheck the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwpmu-plugin-stats\u002Ffaq\u002F\" title=\"Frequently Asked Questions\" rel=\"ugc\">FAQ\u003C\u002Fa> for more details on caching.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Requires a WordPress Multisite Installation\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>JavaScript is required to toggle the list of sites using a plugin\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Development\u003C\u002Fh4>\n\u003Cblockquote>\n\u003Cp>The plugin has reached its end-of-life. No updates and\u002For support after 2018-01-31\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cul>\n\u003Cli>GitHub Repository: \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fwp-repository\u002Fwpmu-plugin-stats\" rel=\"nofollow ugc\">wpmu-plugin-stats\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n","Gives network admins an easy way to see what plugins are actively used on the sites of a multisite installation",17645,60,2,"2018-08-30T09:46:00.000Z","4.9.29","3.8","5.3",[20,77,78,79,24],"plugin-stats","wordpress-mu","wordpress-multiuser","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwpmu-plugin-stats\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwpmu-plugin-stats.3.0.1.zip","2026-04-06T09:54:40.288Z",{"slug":84,"name":85,"version":86,"author":87,"author_profile":88,"description":89,"short_description":90,"active_installs":91,"downloaded":92,"rating":93,"num_ratings":94,"last_updated":95,"tested_up_to":96,"requires_at_least":97,"requires_php":98,"tags":99,"homepage":102,"download_link":103,"security_score":13,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"user-switching","User Switching","1.11.2","John Blackbourn","https:\u002F\u002Fprofiles.wordpress.org\u002Fjohnbillion\u002F","\u003Cp>This plugin allows you to quickly swap between user accounts in WordPress at the click of a button. You’ll be instantly logged out and logged in as your desired user. This is handy for helping customers on WooCommerce sites, membership sites, testing environments, or for any site where administrators need to switch between multiple accounts.\u003C\u002Fp>\n\u003Ch3>Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Switch user: Instantly switch to any user account from the \u003Cem>Users\u003C\u002Fem> screen.\u003C\u002Fli>\n\u003Cli>Switch back: Instantly switch back to your originating account.\u003C\u002Fli>\n\u003Cli>Switch off: Log out of your account but retain the ability to instantly switch back in again.\u003C\u002Fli>\n\u003Cli>Compatible with Multisite, WooCommerce, BuddyPress, and bbPress.\u003C\u002Fli>\n\u003Cli>Compatible with most membership and user management plugins.\u003C\u002Fli>\n\u003Cli>Compatible with most two-factor authentication solutions (see the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fuser-switching\u002Ffaq\u002F\" rel=\"ugc\">FAQ\u003C\u002Fa> for more info).\u003C\u002Fli>\n\u003Cli>Approved for use on enterprise-grade WordPress platforms such as \u003Ca href=\"https:\u002F\u002Fwww.altis-dxp.com\u002F\" rel=\"nofollow ugc\">Altis\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Fwpvip.com\u002F\" rel=\"nofollow ugc\">WordPress VIP\u003C\u002Fa>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Note: User Switching supports versions of WordPress up to three years old, and PHP version 7.4 or higher.\u003C\u002Fp>\n\u003Ch3>Security\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Only users with the ability to edit other users can switch user accounts. By default this is only Administrators on single site installations, and Super Admins on Multisite installations.\u003C\u002Fli>\n\u003Cli>Passwords are not (and cannot be) revealed.\u003C\u002Fli>\n\u003Cli>Uses the cookie authentication system in WordPress when remembering the account(s) you’ve switched from and when switching back.\u003C\u002Fli>\n\u003Cli>Implements the nonce security system in WordPress, meaning only those who intend to switch users can switch.\u003C\u002Fli>\n\u003Cli>Full support for user session validation where appropriate.\u003C\u002Fli>\n\u003Cli>Full support for HTTPS.\u003C\u002Fli>\n\u003Cli>Backed by \u003Ca href=\"https:\u002F\u002Fpatchstack.com\u002Fdatabase\u002Fvdp\u002Fuser-switching\" rel=\"nofollow ugc\">the Patchstack Vulnerability Disclosure Program\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Usage\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Visit the \u003Cem>Users\u003C\u002Fem> menu in WordPress and you’ll see a \u003Cem>Switch To\u003C\u002Fem> link in the list of action links for each user.\u003C\u002Fli>\n\u003Cli>Click this and you will immediately switch into that user account.\u003C\u002Fli>\n\u003Cli>You can switch back to your originating account via the \u003Cem>Switch back\u003C\u002Fem> link on each dashboard screen or in your profile menu in the WordPress toolbar.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>See the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fuser-switching\u002Ffaq\u002F\" rel=\"ugc\">FAQ\u003C\u002Fa> for information about the \u003Cem>Switch Off\u003C\u002Fem> feature.\u003C\u002Fp>\n\u003Ch3>Other Plugins\u003C\u002Fh3>\n\u003Cp>I maintain several other plugins for developers. Check them out:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fquery-monitor\u002F\" rel=\"ugc\">Query Monitor\u003C\u002Fa> is the developer tools panel for WordPress\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-crontrol\u002F\" rel=\"ugc\">WP Crontrol\u003C\u002Fa> lets you view and control what’s happening in the WP-Cron system\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Privacy Statement\u003C\u002Fh3>\n\u003Cp>User Switching does not send data to any third party, nor does it include any third party resources, nor will it ever do so.\u003C\u002Fp>\n\u003Cp>User Switching makes use of browser cookies in order to allow users to switch to another account. Its cookies operate using the same mechanism as the authentication cookies in WordPress core, which means their values contain the user’s \u003Ccode>user_login\u003C\u002Fcode> field in plain text which should be treated as potentially personally identifiable information (PII) for privacy and regulatory reasons (GDPR, CCPA, etc). The names of the cookies are:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>wordpress_user_sw_{COOKIEHASH}\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>wordpress_user_sw_secure_{COOKIEHASH}\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>wordpress_user_sw_olduser_{COOKIEHASH}\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>See also the FAQ for some questions relating to privacy and safety when switching between users.\u003C\u002Fp>\n\u003Ch3>Accessibility Statement\u003C\u002Fh3>\n\u003Cp>User Switching aims to be fully accessible to all of its users. It implements best practices for web accessibility, outputs semantic and structured markup, adheres to the default styles and accessibility guidelines of WordPress, uses the accessibility APIs provided by WordPress and web browsers where appropriate, and is fully accessible via keyboard.\u003C\u002Fp>\n\u003Cp>User Switching should adhere to Web Content Accessibility Guidelines (WCAG) 2.0 at level AA when used with a recent version of WordPress where its admin area itself adheres to these guidelines. If you’ve experienced or identified an accessibility issue in User Switching, please open a thread in \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fuser-switching\u002F\" rel=\"ugc\">the User Switching plugin support forum\u003C\u002Fa> and I’ll address it swiftly.\u003C\u002Fp>\n","Instant switching between user accounts in WordPress and WooCommerce.",200000,5569897,98,238,"2026-02-27T00:17:00.000Z","6.9.4","6.1","7.4",[100,20,84,58,101],"fast-user-switching","woocommerce","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fuser-switching\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fuser-switching.1.11.2.zip",{"slug":105,"name":106,"version":107,"author":108,"author_profile":109,"description":110,"short_description":111,"active_installs":112,"downloaded":113,"rating":114,"num_ratings":115,"last_updated":116,"tested_up_to":96,"requires_at_least":117,"requires_php":98,"tags":118,"homepage":124,"download_link":125,"security_score":13,"vuln_count":14,"unpatched_count":28,"last_vuln_date":126,"fetched_at":30},"safe-redirect-manager","Safe Redirect Manager","2.2.2","10up","https:\u002F\u002Fprofiles.wordpress.org\u002F10up\u002F","\u003Cp>Safely manage your site’s redirects the WordPress way. There are many redirect plugins available. Most of them store redirects in the options table or in custom tables. Most of them provide tons of unnecessary options. Some of them have serious performance implications (404 error logging). Safe Redirect Manager stores redirects as Custom Post Types. This makes your data portable and your website scalable. Safe Redirect Manager is built to handle enterprise level traffic and is used on major publishing websites. The plugin comes with only what you need following the WordPress mantra, decisions not options. Actions and filters make the plugin very extensible.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002F10up\u002Fsafe-redirect-manager\" rel=\"nofollow ugc\">Fork the plugin on GitHub.\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch3>Configuration\u003C\u002Fh3>\n\u003Cp>There are no overarching settings for this plugin. To manage redirects, navigate to the administration panel (“Tools” > “Safe Redirect Manager”).\u003C\u002Fp>\n\u003Cp>Each redirect contains a few fields that you can utilize:\u003C\u002Fp>\n\u003Ch3>“Redirect From”\u003C\u002Fh3>\n\u003Cp>This should be a path relative to the root of your WordPress installation. When someone visits your site with a path that matches this one, a redirect will occur. If your site is located at \u003Ccode>http:\u002F\u002Fexample.com\u002Fwp\u002F\u003C\u002Fcode> and you wanted to redirect \u003Ccode>http:\u002F\u002Fexample.com\u002Fwp\u002Fabout\u003C\u002Fcode> to \u003Ccode>http:\u002F\u002Fexample.com\u003C\u002Fcode>, your “Redirect From” would be \u003Ccode>\u002Fabout\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>Clicking the “Enable Regex” checkbox allows you to use regular expressions in your path. There are many \u003Ca href=\"http:\u002F\u002Fwww.regular-expressions.info\" rel=\"nofollow ugc\">great tutorials\u003C\u002Fa> on regular expressions.\u003C\u002Fp>\n\u003Cp>You can also use wildcards in your “Redirect From” paths. By adding an \u003Ccode>*\u003C\u002Fcode> at the end of a URL, your redirect will match any request that starts with your “Redirect From”. Wildcards support replacements. This means if you have a wildcard in your from path that matches a string, you can have that string replace a wildcard character in your “Redirect To” path. For example, if your “Redirect From” is \u003Ccode>\u002Ftest\u002F*\u003C\u002Fcode>, your “Redirect To” is \u003Ccode>http:\u002F\u002Fgoogle.com\u002F*\u003C\u002Fcode>, and the requested path is \u003Ccode>\u002Ftest\u002Fstring\u003C\u002Fcode>, the user would be redirect to \u003Ccode>http:\u002F\u002Fgoogle.com\u002Fstring\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Ch3>“Redirect To”\u003C\u002Fh3>\n\u003Cp>This should be a path (i.e. \u003Ccode>\u002Ftest\u003C\u002Fcode>) or a URL (i.e. \u003Ccode>http:\u002F\u002Fexample.com\u002Fwp\u002Ftest\u003C\u002Fcode>). If a requested path matches “Redirect From”, they will be redirected here. “Redirect To” supports wildcard and regular expression replacements.\u003C\u002Fp>\n\u003Ch3>“HTTP Status Code”\u003C\u002Fh3>\n\u003Cp>\u003Ca href=\"http:\u002F\u002Fwww.w3.org\u002FProtocols\u002Frfc2616\u002Frfc2616-sec10.html\" rel=\"nofollow ugc\">HTTP status codes\u003C\u002Fa> are numbers that contain information about a request (i.e. whether it was successful, unauthorized, not found, etc). You should almost always use either 302 (temporarily moved) or 301 (permanently moved).\u003C\u002Fp>\n\u003Cp>\u003Cem>Note:\u003C\u002Fem>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Redirects are cached using the Transients API. Cache busts occur when redirects are added, updated, and deleted so you shouldn’t be serving stale redirects.\u003C\u002Fli>\n\u003Cli>By default the plugin only allows at most 1000 redirects to prevent performance issues. There is a filter \u003Ccode>srm_max_redirects\u003C\u002Fcode> that you can utilize to up this number.\u003C\u002Fli>\n\u003Cli>“Redirect From” and requested paths are case insensitive by default.\u003C\u002Fli>\n\u003Cli>Developers can use \u003Ccode>srm_additional_status_codes\u003C\u002Fcode> filter to add status codes if needed.\u003C\u002Fli>\n\u003Cli>Rules set with 403 and 410 status codes are handled by applying the HTTP status code and render the default WordPress \u003Ccode>wp_die\u003C\u002Fcode> screen with an optional message.\u003C\u002Fli>\n\u003Cli>Rules set with a 404 status code will apply the status code and render the 404 template.\u003C\u002Fli>\n\u003Cli>Browsers heavily cache 301 (permanently moved) redirects. It’s recommended to test your permanent redirects using the 302 (temporarily moved) status code before changing them to 301 permanently moved.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Developer Documentation\u003C\u002Fh3>\n\u003Cp>Safe Redirect Manager includes a number of actions and filters developers can make use of. These are documented on the \u003Ca href=\"http:\u002F\u002F10up.github.io\u002Fsafe-redirect-manager\u002F\" rel=\"nofollow ugc\">Safe Redirect Manager developer documentation\u003C\u002Fa> micro-site.\u003C\u002Fp>\n","Safely manage your website's HTTP redirects.",40000,1943909,94,78,"2026-01-04T21:19:00.000Z","6.5",[119,120,121,122,123],"http-redirects","multisite-redirects","redirect-manager","safe-http-redirection","url-redirection","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fsafe-redirect-manager","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsafe-redirect-manager.2.2.2.zip","2022-06-19 00:00:00",{"slug":128,"name":129,"version":130,"author":131,"author_profile":132,"description":133,"short_description":134,"active_installs":135,"downloaded":136,"rating":114,"num_ratings":137,"last_updated":138,"tested_up_to":96,"requires_at_least":139,"requires_php":98,"tags":140,"homepage":146,"download_link":147,"security_score":148,"vuln_count":51,"unpatched_count":28,"last_vuln_date":149,"fetched_at":30},"inactive-logout","Inactive Logout","3.6.1","Deepen Bajracharya","https:\u002F\u002Fprofiles.wordpress.org\u002Fj_3rk\u002F","\u003Cp>Protect your WordPress users’ sessions from prying eyes and snoopers!\u003C\u002Fp>\n\u003Cp>The Inactive Logout plugin automatically terminates idle user sessions, safeguarding your site if users leave their sessions unattended.\u003C\u002Fp>\n\u003Cp>A simple plugin which is easy to configure and use. After installing and activating it, just set the idle timeout from the plugin settings. From then on, any unattended idle WordPress sessions will be automatically terminated. You can also display a custom message to users, warning them that their session is about to end.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Try it out ==> \u003Ca href=\"https:\u002F\u002Ftastewp.org\u002Fplugins\u002Finactive-logout\u002F\" title=\"Demo Link\" rel=\"nofollow ugc\">Demo\u003C\u002Fa>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>FEATURES:\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Change idle timeout time.\u003C\u002Fli>\n\u003Cli>Count down of 10 seconds before actual logout. You can remove this feature if you dont want it.\u003C\u002Fli>\n\u003Cli>Add only \u003Cstrong>Wake Up!\u003C\u002Fstrong> message where user will not logout but instead a wakeup message will be shown upon inactive.\u003C\u002Fli>\n\u003Cli>Custom Popup Message.\u003C\u002Fli>\n\u003Cli>Show idle message for non authenticated users or redirect them.\u003C\u002Fli>\n\u003Cli>Concurrent user logouts.\u003C\u002Fli>\n\u003Cli>Toast notification on Logout.\u003C\u002Fli>\n\u003Cli>Redirect to a Different Page instead of Popup box. Create a page such as timeout page and add your content there by creating a blank template or style it as you wish according to your theme.\u003C\u002Fli>\n\u003Cli>Multiple User Role Configurations for individual timeout and session logout redirects.\u003C\u002Fli>\n\u003Cli>Logout to custom page or existing page.\u003C\u002Fli>\n\u003Cli>Clean UI\u003C\u002Fli>\n\u003Cli>WooCommerce Supported.\u003C\u002Fli>\n\u003Cli>Multisite Support: Override all sites with one setting.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>EXTEND OTHER FEATURES:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Few of the key features to \u003Cstrong>\u003Ca href=\"https:\u002F\u002Finactive-logout.com\u002Fpricing\u002F\" title=\"Inactive Logout Pro\" rel=\"nofollow ugc\">Inactive Logout Pro\u003C\u002Fa>\u003C\u002Fstrong>:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Auto browser close logout after defined duration.\u003C\u002Fli>\n\u003Cli>Fully functional multi-tab support.\u003C\u002Fli>\n\u003Cli>User Based Logout\u003C\u002Fli>\n\u003Cli>Track Visitors based on \u003Cstrong>(Login time, logout time, browser, online status, session duration, role, os, IP)\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>Force Logout All Users\u003C\u002Fli>\n\u003Cli>Logout Specific User(s)\u003C\u002Fli>\n\u003Cli>Bulk Logout Users\u003C\u002Fli>\n\u003Cli>Concurrent Login Limits.\u003C\u002Fli>\n\u003Cli>Last Login Activity\u003C\u002Fli>\n\u003Cli>Override Multiple Login priority\u003C\u002Fli>\n\u003Cli>User Lock whenever certain limit login has been reached.\u003C\u002Fli>\n\u003Cli>Track user login sessions.\u003C\u002Fli>\n\u003Cli>Logout redirects.\u003C\u002Fli>\n\u003Cli>Login redirects.\u003C\u002Fli>\n\u003Cli>Email notification and email template overrides for Locked concurrent session.\u003C\u002Fli>\n\u003Cli>Disable inactive logout for specified pages according to your need. Check this \u003Cstrong>\u003Ca href=\"https:\u002F\u002Fgist.github.com\u002Ftechies23\u002F6d2852eedd6ae56c486056e021e4ee48\" title=\"documentation\" rel=\"nofollow ugc\">Documentation\u003C\u002Fa>\u003C\u002Fstrong> for additional post type support.\u003C\u002Fli>\n\u003Cli>Disable native wordpress login popup after logout\u003C\u002Fli>\n\u003Cli>Modal Customizer\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>**See the \u003Ca href=\"https:\u002F\u002Finactive-logout.com\u002F\" title=\"Inactive Logout\" rel=\"nofollow ugc\">Inactive Logout\u003C\u002Fa> homepage for further information.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Please consider giving a \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Finactive-logout\u002Freviews\u002F#new-post\" title=\"5 star thumbs up\" rel=\"ugc\">5 star thumbs up\u003C\u002Fa> if you found this useful.\u003C\u002Fstrong>\u003C\u002Fp>\n","Automatically logout idle user sessions, with logout redirections and concurrent limit logins all in one place.",20000,659133,106,"2025-12-09T05:09:00.000Z","6.6",[141,142,143,144,145],"concurrent-login-limit","idle-logout","logout","security","user-redirection","https:\u002F\u002Finactive-logout.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Finactive-logout.3.6.1.zip",97,"2025-10-31 13:27:51",{"attackSurface":151,"codeSignals":162,"taintFlows":169,"riskAssessment":170,"analyzedAt":173},{"hooks":152,"ajaxHandlers":158,"restRoutes":159,"shortcodes":160,"cronEvents":161,"entryPointCount":28,"unprotectedCount":28},[153],{"type":154,"name":21,"callback":155,"file":156,"line":157},"action","checkAccess","Plugin.php",20,[],[],[],[],{"dangerousFunctions":163,"sqlUsage":164,"outputEscaping":166,"fileOperations":28,"externalRequests":28,"nonceChecks":28,"capabilityChecks":28,"bundledLibraries":168},[],{"prepared":28,"raw":28,"locations":165},[],{"escaped":28,"rawEcho":28,"locations":167},[],[],[],{"summary":171,"deductions":172},"The plugin 'redirect-multisite-user-to-their-own-site' v1.1.2 demonstrates an exceptionally strong security posture based on the provided static analysis. The absence of any identified entry points, including AJAX handlers, REST API routes, shortcodes, and cron events, significantly reduces the potential attack surface. Furthermore, the code analysis reveals no dangerous functions, all SQL queries utilize prepared statements, and all output is properly escaped. The lack of file operations and external HTTP requests further bolsters its security. Taint analysis also shows no identified flows with unsanitized paths, indicating a lack of common vulnerabilities like cross-site scripting (XSS) or path traversal.\n\nThe plugin's vulnerability history is also clean, with no recorded CVEs of any severity. This, combined with the code analysis, suggests that the developers have implemented robust security practices. However, it's worth noting the complete absence of nonces and capability checks. While the current lack of entry points mitigates the immediate risk, this could become a concern if the plugin were to evolve and introduce new functionalities that might expose these checks.\n\nIn conclusion, the 'redirect-multisite-user-to-their-own-site' v1.1.2 plugin appears to be very secure, with a commendable absence of common vulnerabilities and a minimal attack surface. The developers have clearly prioritized security in its current implementation. The only minor area for potential future consideration would be the implementation of nonces and capability checks if the plugin's feature set expands.",[],"2026-04-16T12:11:21.029Z",{"wat":175,"direct":180},{"assetPaths":176,"generatorPatterns":177,"scriptPaths":178,"versionParams":179},[],[],[],[],{"cssClasses":181,"htmlComments":182,"htmlAttributes":183,"restEndpoints":184,"jsGlobals":185,"shortcodeOutput":186},[],[],[],[],[],[],{"error":188,"url":189,"statusCode":190,"statusMessage":191,"message":191},true,"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Fredirect-multisite-user-to-their-own-site\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":193,"versions":194},5,[195,202,209,216,223],{"version":6,"download_url":196,"svn_tag_url":197,"released_at":29,"has_diff":198,"diff_files_changed":199,"diff_lines":29,"trac_diff_url":200,"vulnerabilities":201,"is_current":188},"https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fredirect-multisite-user-to-their-own-site.1.1.2.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fredirect-multisite-user-to-their-own-site\u002Ftags\u002F1.1.2\u002F",false,[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fredirect-multisite-user-to-their-own-site%2Ftags%2F1.1.1&new_path=%2Fredirect-multisite-user-to-their-own-site%2Ftags%2F1.1.2",[],{"version":203,"download_url":204,"svn_tag_url":205,"released_at":29,"has_diff":198,"diff_files_changed":206,"diff_lines":29,"trac_diff_url":207,"vulnerabilities":208,"is_current":198},"1.1.1","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fredirect-multisite-user-to-their-own-site.1.1.1.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fredirect-multisite-user-to-their-own-site\u002Ftags\u002F1.1.1\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fredirect-multisite-user-to-their-own-site%2Ftags%2F1.1.0&new_path=%2Fredirect-multisite-user-to-their-own-site%2Ftags%2F1.1.1",[],{"version":210,"download_url":211,"svn_tag_url":212,"released_at":29,"has_diff":198,"diff_files_changed":213,"diff_lines":29,"trac_diff_url":214,"vulnerabilities":215,"is_current":198},"1.1.0","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fredirect-multisite-user-to-their-own-site.1.1.0.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fredirect-multisite-user-to-their-own-site\u002Ftags\u002F1.1.0\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fredirect-multisite-user-to-their-own-site%2Ftags%2F1.0.1&new_path=%2Fredirect-multisite-user-to-their-own-site%2Ftags%2F1.1.0",[],{"version":217,"download_url":218,"svn_tag_url":219,"released_at":29,"has_diff":198,"diff_files_changed":220,"diff_lines":29,"trac_diff_url":221,"vulnerabilities":222,"is_current":198},"1.0.1","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fredirect-multisite-user-to-their-own-site.1.0.1.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fredirect-multisite-user-to-their-own-site\u002Ftags\u002F1.0.1\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fredirect-multisite-user-to-their-own-site%2Ftags%2F1.0.0&new_path=%2Fredirect-multisite-user-to-their-own-site%2Ftags%2F1.0.1",[],{"version":224,"download_url":225,"svn_tag_url":226,"released_at":29,"has_diff":198,"diff_files_changed":227,"diff_lines":29,"trac_diff_url":29,"vulnerabilities":228,"is_current":198},"1.0.0","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fredirect-multisite-user-to-their-own-site.1.0.0.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fredirect-multisite-user-to-their-own-site\u002Ftags\u002F1.0.0\u002F",[],[]]