[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fl1hHErXkNcMg0nTOJMt8IyHb0eyv8tLNdycuuM8qIx8":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":22,"download_link":23,"security_score":24,"vuln_count":25,"unpatched_count":25,"last_vuln_date":26,"fetched_at":27,"vulnerabilities":28,"developer":29,"crawl_stats":26,"alternatives":37,"analysis":136,"fingerprints":180},"mw-auth","MW Auth","1.2","Takashi Kitajima","https:\u002F\u002Fprofiles.wordpress.org\u002Finc2734\u002F","\u003Cp>This plugin allows only users to authenticate to WordPress.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Subscriber can’t see dashboad.\u003C\u002Fli>\n\u003Cli>Subscriber can’t see Admin Bar.\u003C\u002Fli>\n\u003Cli>Add ‘Disallow: \u002F’ in robots.txt\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>このプラグインはWordPressで認証されたユーザーのみ許可します。\u003C\u002Fp>\n\u003Cp>・「購読者」はダッシュボードに入れないようにします。\u003Cbr \u002F>\n・「購読者」には管理バーを表示しません。\u003Cbr \u002F>\n・robots.txt に ‘Disallow: \u002F’ を追加します。\u003C\u002Fp>\n","This plugin allows only users to authenticate to WordPress.",40,2711,100,2,"2014-05-31T01:36:00.000Z","3.9.40","3.4","",[20,21],"auth","authenticate","http:\u002F\u002F2inc.org","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fmw-auth.1.2.zip",85,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":33,"avg_patch_time_days":34,"trust_score":35,"computed_at":36},"inc2734",11,330630,89,122,71,"2026-04-04T05:52:10.721Z",[38,60,81,101,117],{"slug":39,"name":40,"version":41,"author":42,"author_profile":43,"description":44,"short_description":45,"active_installs":46,"downloaded":47,"rating":48,"num_ratings":31,"last_updated":49,"tested_up_to":50,"requires_at_least":51,"requires_php":52,"tags":53,"homepage":58,"download_link":59,"security_score":13,"vuln_count":25,"unpatched_count":25,"last_vuln_date":26,"fetched_at":27},"json-api-auth","JSON API Auth","3.0.0","Ali Qureshi","https:\u002F\u002Fprofiles.wordpress.org\u002Fparorrey\u002F","\u003Cp>JSON API Auth extends the JSON API Plugin to allow RESTful user authentication.\u003C\u002Fp>\n\u003Cp>JSON API Plugin, that is required, was closed on August 7, 2019 from WordPress repository. You can download \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FPI-Media\u002Fjson-api\" rel=\"nofollow ugc\">JSON API Plugin\u003C\u002Fa> from https:\u002F\u002Fgithub.com\u002FPI-Media\u002Fjson-api until it is republished and available on WordPress.\u003C\u002Fp>\n\u003Cp>Features include:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>Generate Auth Cookie for user authentication\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Validate Auth Cookie\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Get Current User Info\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>For documentation: See ‘Other Notes’ tab above for usage examples.\u003C\u002Fp>\n\u003Cp>Credits: http:\u002F\u002Fwww.parorrey.com\u002Fsolutions\u002Fjson-api-auth\u002F\u003C\u002Fp>\n","Extends the JSON API Plugin for RESTful user authentication",800,78995,94,"2025-07-29T11:41:00.000Z","6.8.5","3.0.1","5.3",[54,55,56,57],"api","authenticate-user","json-api","wordpress-user-authentication","http:\u002F\u002Fwww.parorrey.com\u002Fsolutions\u002Fjson-api-auth\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fjson-api-auth.3.0.0.zip",{"slug":61,"name":62,"version":63,"author":64,"author_profile":65,"description":66,"short_description":67,"active_installs":68,"downloaded":69,"rating":70,"num_ratings":71,"last_updated":72,"tested_up_to":73,"requires_at_least":74,"requires_php":18,"tags":75,"homepage":79,"download_link":80,"security_score":24,"vuln_count":25,"unpatched_count":25,"last_vuln_date":26,"fetched_at":27},"http-digest-auth","HTTP Digest Authentication","1.2.1","Jesin A","https:\u002F\u002Fprofiles.wordpress.org\u002Fjesin\u002F","\u003Cp>This plugin adds an additional layer of protection for the \u003Cstrong>wp-login.php\u003C\u002Fstrong> page using \u003Ca href=\"http:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FDigest_access_authentication\" rel=\"nofollow ugc\">HTTP Digest Authentication\u003C\u002Fa> with the PHP \u003Ca href=\"http:\u002F\u002Fphp.net\u002Fheader\" rel=\"nofollow ugc\">header()\u003C\u002Fa> function.\u003Cbr \u002F>\nSo it doesn’t require configuring web server files like \u003Cem>.htaccess\u003C\u002Fem> or \u003Ca href=\"https:\u002F\u002Fwebsistent.com\u002Ftools\u002Fhtdigest-generator-tool\u002F\" rel=\"nofollow ugc\">\u003Cem>.htdigest\u003C\u002Fem>\u003C\u002Fa> and works on all web hosting environments.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Important:\u003C\u002Fstrong> If you already have a plugin which does HTTP Authentication please deactivate it before activating this plugin. Similarly if you have configured your web server to do HTTP authentication on the wp-login.php file please remove it before using this plugin.\u003C\u002Fp>\n\u003Cp>If you are using FastCGI PHP this plugin may keep prompting for the credentials even if you enter the right pair, in this case use the following in your \u003Cstrong>\u003Ccode>.htaccess\u003C\u002Fcode>\u003C\u002Fstrong> file\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003CIfModule mod_setenvif.c>\nSetEnvIfNoCase ^Authorization$ \"(.+)\" PHP_AUTH_DIGEST=$1\n\u003C\u002FIfModule>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Advantages of HTTP Digest Authentication\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Digest Authentication is very much safer than HTTP Basic Authentication whose credentials can be easily decoded with a \u003Ca href=\"http:\u002F\u002Fwww.base64decode.org\u002F\" rel=\"nofollow ugc\">base64 decoder\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>From Wikipedia on \u003Ca href=\"http:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FBasic_access_authentication\" rel=\"nofollow ugc\">HTTP Basic Authentication\u003C\u002Fa>:\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cblockquote>\n\u003Cp>\u003Cem>The BA (Basic Authentication) mechanism provides no confidentiality protection for the transmitted credentials. They are merely encoded with BASE64 in transit, but not encrypted or hashed in any way.\u003C\u002Fem>\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cul>\n\u003Cli>Digest Authentication on the other hand uses \u003Ca href=\"https:\u002F\u002Fwebsistent.com\u002Ftools\u002Fmd5-encryption-tool\u002F\" rel=\"nofollow ugc\">MD5\u003C\u002Fa> on the credentials making it “one way” \u003C\u002Fli>\n\u003Cli>Uses server and client \u003Ca href=\"http:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FCryptographic_nonce\" rel=\"nofollow ugc\">nonce\u003C\u002Fa>s to prevent replay attacks\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Features of the HTTP Digest Auth plugin\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Works using PHP header() function and doesn’t require modification of service config files (like .htaccess, nginx.conf etc)\u003C\u002Fli>\n\u003Cli>Supports HTTP credentials for each WordPress user\u003C\u002Fli>\n\u003Cli>Clears the HTTP Digest credentials when the user logs out of WordPress (more on this in the FAQ)\u003C\u002Fli>\n\u003Cli>Verifies if both the HTTP and WordPress credentials are of the same user (this is the default behavior and can be changed)\u003C\u002Fli>\n\u003Cli>Works on all major Web Servers (Tested on Apache, Nginx and Lighttpd)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Plugin Behavior\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>When this plugin is activated for the first time all WordPress users will have the following Digest credentials\u003Cbr \u002F>\nUsername: \u003CWordPress username>\u003Cbr \u002F>\nPassword: password\u003Cbr \u002F>\nThis can be changed from \u003Cstrong>Users > Your Profile\u003C\u002Fstrong>.\u003C\u002Fli>\n\u003Cli>After activating this plugin for the first time you’ll be prompted for HTTP credentials when you logout\u003C\u002Fli>\n\u003Cli>Similarly if you change your HTTP username or password you’ll be prompted for this when you logout\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Available languages\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>English\u003C\u002Fli>\n\u003Cli>Serbo-Croatian by \u003Ca href=\"http:\u002F\u002Fwww.webhostinghub.com\u002F\" rel=\"nofollow ugc\">Borisa Djuraskovic\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The \u003Ca href=\"https:\u002F\u002Fwebsistent.com\u002Fwordpress-plugins\u002Fhttp-digest-authentication\u002F\" rel=\"nofollow ugc\">HTTP Digest Authentication Plugin\u003C\u002Fa> official homepage.\u003C\u002Fp>\n","Protect your wp-login.php page with HTTP Digest Authentication without the need of adding web server modules or changing config files.",10,4957,80,5,"2017-11-25T14:25:00.000Z","4.9.29","3.1.0",[20,21,76,77,78],"hacking","http-digest","login","https:\u002F\u002Fwebsistent.com\u002Fwordpress-plugins\u002Fhttp-digest-authentication\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhttp-digest-auth.1.2.1.zip",{"slug":82,"name":83,"version":84,"author":85,"author_profile":86,"description":87,"short_description":88,"active_installs":68,"downloaded":89,"rating":25,"num_ratings":25,"last_updated":90,"tested_up_to":91,"requires_at_least":92,"requires_php":18,"tags":93,"homepage":99,"download_link":100,"security_score":24,"vuln_count":25,"unpatched_count":25,"last_vuln_date":26,"fetched_at":27},"mbc-smtp-flex","MBC SMTP Flex","0.5","yogaboy","https:\u002F\u002Fprofiles.wordpress.org\u002Fyogaboy\u002F","\u003Cp>Use SMTP with authentication to deliver messages from WordPress. Intercepts wp_mail function to allow you to define the server, port, connection security and credentials.\u003C\u002Fp>\n\u003Cp>Designed initially as a replacement for the wp_mail function, this plugin uses the core WordPress mail functions and extends only the settings needed to allow connection to third-party mailing systems that require authentication and have sender and recipient restrictions.\u003C\u002Fp>\n\u003Cp>Particularly good with Amazon SES where there are tight restrictions for sender lists and in sandbox mode only validated addresses may receive messages.\u003C\u002Fp>\n\u003Cp>You can also simply use this to force sender and receivers for any messages from WordPress as well as set the default name in messages originating from your site.\u003C\u002Fp>\n\u003Cp>Features:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Flexible configuration works with basically any mail service and protocol\u003C\u002Fli>\n\u003Cli>Test function will allow you to diagnose specific errors in the email transmission\u003C\u002Fli>\n\u003Cli>Able to handle Amazon Sandbox restrictions by overriding the recipient and sending only to an authorized address\u003C\u002Fli>\n\u003Cli>Debug mode to capture transmission logs from phpmailer\u003C\u002Fli>\n\u003C\u002Ful>\n","Extends wp_mail function to allow you to define the server, port, connection security and credentials.",1243,"2015-12-10T20:12:00.000Z","4.3.34","3.5.1",[94,95,96,97,98],"amazon","authenticated-mail","ses","smtp","wp_mail","http:\u002F\u002Fbistromatics.com\u002Fmbc-smtp-flex","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fmbc-smtp-flex.zip",{"slug":102,"name":103,"version":104,"author":105,"author_profile":106,"description":107,"short_description":108,"active_installs":68,"downloaded":109,"rating":110,"num_ratings":111,"last_updated":112,"tested_up_to":16,"requires_at_least":74,"requires_php":18,"tags":113,"homepage":115,"download_link":116,"security_score":24,"vuln_count":25,"unpatched_count":25,"last_vuln_date":26,"fetched_at":27},"two-factor-auth","Two Factor Auth","4.4","oskarhane","https:\u002F\u002Fprofiles.wordpress.org\u002Foskarhane\u002F","\u003Cp>Secure WordPress login with this two factor auth. Users will have to enter an One Time Password when they log in.\u003C\u002Fp>\n\u003Ch4>Why You Need This\u003C\u002Fh4>\n\u003Cp>Users can have common or weak passwords that lets hackers\u002Fbots brute-force your WordPress site and gain access to your files and place malware there.\u003Cbr \u002F>\nJust like happend not that long ago: \u003Ca href=\"http:\u002F\u002Ftechcrunch.com\u002F2013\u002F04\u002F12\u002Fhackers-point-large-botnet-at-wordpress-sites-to-steal-admin-passwords-and-gain-server-access\u002F\" rel=\"nofollow ugc\">Article on TechCrunch\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>If all sites would have used this plugin, this would never happend.\u003Cbr \u002F>\nIt doesn’t matter how weak your users passwords are, no one can gain access to your WordPress site\u003Cbr \u002F>\nwithout already having access to the users mobile phone or email inbox (depending on how the user gets his OTP).\u003C\u002Fp>\n\u003Ch4>How Does It Work?\u003C\u002Fh4>\n\u003Cp>This plugin uses the industry standard algorithm \u003Ca href=\"http:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FTime-based_One-time_Password_Algorithm\" rel=\"nofollow ugc\">TOTP\u003C\u002Fa> or \u003Ca href=\"http:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FHMAC-based_One-time_Password_Algorithm\" rel=\"nofollow ugc\">HOTP\u003C\u002Fa> for creating One Time Passwords.\u003Cbr \u002F>\nA OTP is valid for a certain time and after that a new code has to be entered.\u003C\u002Fp>\n\u003Cp>You can now choose to use third party apps like \u003Ca href=\"http:\u002F\u002Fcode.google.com\u002Fp\u002Fgoogle-authenticator\u002F\" rel=\"nofollow ugc\">Google Authenticator\u003C\u002Fa> which is available for most mobile platforms. You can really use any\u003Cbr \u002F>\nthird party app that supports TOTP\u002FHOTP that generates 6 digits OTP’s.\u003Cbr \u002F>\nOr, as before, you can choose to get your One Time Passwords by email.\u003C\u002Fp>\n\u003Cp>Since you have to enter a secret code to third party apps, email is the default way of delivering One Time Passwords. Your\u003Cbr \u002F>\nusers will have to activate delivery by third party apps themselves.\u003C\u002Fp>\n\u003Ch4>Easy To Use\u003C\u002Fh4>\n\u003Cp>Just install this plugin and you’re all set. There’s really nothing more to it.\u003Cbr \u002F>\nIf you want to use a third party app, goto Two Factor Auth in the admin menu and activate it and set up your app.\u003Cbr \u002F>\nGeneral settings can be found uner Settings -> Two Factor Auth in admin menu. Settings for each individual user\u003Cbr \u002F>\ncan be found at the root level of the admin menu, in Two Factor Auth.\u003Cbr \u002F>\nA bit more work to get logged in, but a whole lot more secure!\u003C\u002Fp>\n\u003Cp>If you use WooCommerce or other plugins that make custom login forms, you will not be able to login through those anymore.\u003Cbr \u002F>\nI will be adding a plugin that puts a One Time Password field to WooCommerce. If you use some other plugin that needs\u003Cbr \u002F>\nsupport for this, let me know in the support forum.\u003C\u002Fp>\n\u003Ch4>TOTP or HOTP\u003C\u002Fh4>\n\u003Cp>Which algorithm you and your users choose doesn’t really matter. The time based TOTP is a bit more secure since a One Time\u003Cbr \u002F>\nPassword is valid only for a certain amount of time. But this requires the server time to be in sync the clients time (if\u003Cbr \u002F>\nthe OTP isn’t delivered by email). This is often hard to do with embedded clients and the event based HOTP is then a better choice.\u003Cbr \u002F>\nIf you have a somewhat slow email server and have chosen email delivery, you might not get the TOTP in time.\u003C\u002Fp>\n\u003Cp>Conslusion: Choose which ever you want. TOTP is a little bit safer since OTP:s only are valid for a short period.\u003C\u002Fp>\n\u003Cp>Note that email delivery users always uses the site default algorithm, which you can set on the settings page. Third party\u003Cbr \u002F>\napps users can choose which one they want.\u003C\u002Fp>\n\u003Ch4>Is this really Two Factor Auth?\u003C\u002Fh4>\n\u003Cp>Before version 3.0 this plugin had ‘kind of’ two factor auth where the OTP was delivered to an email address.\u003Cbr \u002F>\nSince version 3.0 you can have real two factor auth if you activate the Third Party Apps delivery type.\u003C\u002Fp>\n\u003Cp>Read more about \u003Ca href=\"http:\u002F\u002Foskarhane.com\u002Ftwo-factor-auth-explained\u002F\" rel=\"nofollow ugc\">what two factor auth means >>\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>See http:\u002F\u002Foskarhane.com\u002Fplugin-two-factor-auth-for-wordpress\u002F for more info.\u003C\u002Fp>\n","Secure WordPress login with Two Factor Auth. Users will have to enter an One Time Password when they log in.",14401,92,22,"2014-07-29T12:54:00.000Z",[20,21,78,114,102],"security","http:\u002F\u002Foskarhane.com\u002Fplugin-two-factor-auth-for-wordpress","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ftwo-factor-auth.4.4.zip",{"slug":118,"name":119,"version":120,"author":121,"author_profile":122,"description":123,"short_description":124,"active_installs":68,"downloaded":125,"rating":13,"num_ratings":126,"last_updated":127,"tested_up_to":128,"requires_at_least":129,"requires_php":18,"tags":130,"homepage":134,"download_link":135,"security_score":24,"vuln_count":25,"unpatched_count":25,"last_vuln_date":26,"fetched_at":27},"wp-secure-login","WP Secure Login","1.1","brijeshk89","https:\u002F\u002Fprofiles.wordpress.org\u002Fbrijeshk89\u002F","\u003Cp>WP Secure Login adds a security layer and 2 step authentication to your WordPress site by asking a One Time Password in addition to the username and password on the login page. The One Time Password is displayed on your smartphone using Google Authenticator app (available in market place for FREE). The One Time Password is re-generated at regular intervals which can be customized from admin panel. As soon as the new OTP is generated the old ones are marked as invalid.\u003C\u002Fp>\n\u003Cp>One Time Password needs to be configured once by every user from Edit Profile page.\u003C\u002Fp>\n\u003Cp>Features in WP Secure Login 1.1 include:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>2 Step Authentication\u003C\u002Fli>\n\u003Cli>Unique Secret key for each user\u003C\u002Fli>\n\u003Cli>Configure\u002FRe-Configure WP Secure Login\u003C\u002Fli>\n\u003Cli>Unique One Time Passwords generated by Google Authenticator App\u003C\u002Fli>\n\u003Cli>Supported on iOS\u002FAndroid\u002FBlackberry smartphones\u003C\u002Fli>\n\u003Cli>Completely FREE\u003C\u002Fli>\n\u003Cli>Licensed under GNU GPL version 3\u003C\u002Fli>\n\u003Cli>Safe & Secure\u003C\u002Fli>\n\u003C\u002Ful>\n","WP Secure Login adds a security layer and 2 step authentication to your WordPress site by asking a One Time Password in addition to the username and p …",2693,1,"2014-09-17T18:12:00.000Z","4.0.38","3.0",[131,21,132,78,133],"2-step","authentication","secure","http:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fwp-secure-login\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-secure-login.1.1.zip",{"attackSurface":137,"codeSignals":167,"taintFlows":175,"riskAssessment":176,"analyzedAt":179},{"hooks":138,"ajaxHandlers":163,"restRoutes":164,"shortcodes":165,"cronEvents":166,"entryPointCount":25,"unprotectedCount":25},[139,145,150,154,159],{"type":140,"name":141,"callback":142,"file":143,"line":144},"action","template_redirect","logged_in","mw-auth.php",41,{"type":146,"name":147,"callback":148,"file":143,"line":149},"filter","robots_txt","disallow_robots_txt",42,{"type":140,"name":151,"callback":152,"file":143,"line":153},"admin_menu","redirect",43,{"type":146,"name":155,"callback":156,"priority":157,"file":143,"line":158},"admin_bar_menu","remove_admin_bar_menu",9999,44,{"type":140,"name":160,"callback":161,"file":143,"line":162},"wp_before_admin_bar_render","add_admin_bar_menu",45,[],[],[],[],{"dangerousFunctions":168,"sqlUsage":169,"outputEscaping":171,"fileOperations":25,"externalRequests":25,"nonceChecks":25,"capabilityChecks":173,"bundledLibraries":174},[],{"prepared":25,"raw":25,"locations":170},[],{"escaped":25,"rawEcho":25,"locations":172},[],3,[],[],{"summary":177,"deductions":178},"The \"mw-auth\" v1.2 plugin exhibits a very strong security posture based on the provided static analysis. There are no identified AJAX handlers, REST API routes, shortcodes, or cron events, resulting in a zero attack surface. This lack of entry points significantly minimizes the potential for external interaction and exploitation. Furthermore, the code analysis indicates a clean codebase with no dangerous functions, no raw SQL queries, all output properly escaped, no file operations, and no external HTTP requests. The presence of capability checks suggests an awareness of authorization, although the absence of nonce checks on the zero AJAX handlers is noted but is not a direct risk due to their non-existence. The vulnerability history is also pristine, with zero known CVEs, indicating a history of secure development and maintenance. This overall lack of identified weaknesses and a clean history points to a highly secure plugin. However, it's important to note that the absence of specific security mechanisms like nonce checks, while not currently a risk, could become one if new entry points were introduced in future versions without corresponding security measures. The current assessment, based on the provided data, is that the plugin is exceptionally secure.",[],"2026-03-16T22:09:14.756Z",{"wat":181,"direct":190},{"assetPaths":182,"generatorPatterns":185,"scriptPaths":186,"versionParams":187},[183,184],"\u002Fwp-content\u002Fplugins\u002Fmw-auth\u002Fcss\u002Fmw-auth.css","\u002Fwp-content\u002Fplugins\u002Fmw-auth\u002Fjs\u002Fmw-auth.js",[],[184],[188,189],"mw-auth\u002Fcss\u002Fmw-auth.css?ver=","mw-auth\u002Fjs\u002Fmw-auth.js?ver=",{"cssClasses":191,"htmlComments":192,"htmlAttributes":193,"restEndpoints":194,"jsGlobals":195,"shortcodeOutput":196},[],[],[],[],[],[]]