[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fKDBTkogBjN3BH2CMCILXBBcJxM_HQxPz4lL82BTYvLI":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":21,"download_link":22,"security_score":23,"vuln_count":13,"unpatched_count":13,"last_vuln_date":24,"fetched_at":25,"vulnerabilities":26,"developer":27,"crawl_stats":24,"alternatives":35,"analysis":117,"fingerprints":186},"force-user-login-by-webline","Force Login by Webline","1.0.10","WeblineIndia","https:\u002F\u002Fprofiles.wordpress.org\u002Fweblineindia\u002F","\u003Cp>This plugin provides a feature to make your site restricted and user is required to login to view protected pages. It has two setting in admin, which are as below:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Enable Force Login : This will enable force login feature for your site.\u003C\u002Fli>\n\u003Cli>Page to Redirect After login: You can select page from the list of added page, user will land to selected page after login. If not selected then it will redirect user to home page\u003C\u002Fli>\n\u003C\u002Ful>\n","This plugin provides a feature to make your site restricted and user is required to login to view protected pages.",40,3801,0,"2024-12-10T12:53:00.000Z","6.7.5","3.2","",[19,20],"force-login","login-restriction","http:\u002F\u002Fwww.weblineindia.com","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fforce-user-login-by-webline.1.0.10.zip",92,null,"2026-03-15T15:16:48.613Z",[],{"slug":28,"display_name":7,"profile_url":8,"plugin_count":29,"total_installs":30,"avg_security_score":31,"avg_patch_time_days":32,"trust_score":33,"computed_at":34},"weblineindia",13,5180,91,54,82,"2026-04-04T10:39:23.607Z",[36,59,80,99],{"slug":37,"name":38,"version":39,"author":40,"author_profile":41,"description":42,"short_description":43,"active_installs":44,"downloaded":45,"rating":23,"num_ratings":46,"last_updated":47,"tested_up_to":48,"requires_at_least":49,"requires_php":50,"tags":51,"homepage":56,"download_link":57,"security_score":58,"vuln_count":13,"unpatched_count":13,"last_vuln_date":24,"fetched_at":25},"login-ip-country-restriction","Login IP & Country Restriction","6.8.1","Iulia Cazan","https:\u002F\u002Fprofiles.wordpress.org\u002Fiulia-cazan\u002F","\u003Cp>This plugin hooks in the authenticate filter. By default, the plugin is set to allow all access and you can configure the plugin to allow the login only from some specified IPs or the specified countries. PLEASE MAKE SURE THAT YOU CONFIGURE THE PLUGIN TO ALLOW YOUR OWN ACCESS. If you set a restriction by IP, then you have to add your own IP (if you are using the plugin in a local setup the IP is 127.0.0.1 or ::1, this is added in your list by default). If you set a restriction by country, then you have to select from the list of countries at least your country. Both types of restrictions work independent, so you can set only one type of restriction or both if you want. Also, you can configure the redirects to frontpage when the URLs are accessed by someone that has a restriction. The restriction is either by country, or not in the specified IPs list.\u003C\u002Fp>\n\u003Ch3>License\u003C\u002Fh3>\n\u003Cp>This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.\u003C\u002Fp>\n","Tighten your website security and fight against dictionary bot attacks originating from other countries, by denying access.",7000,112297,51,"2025-11-22T14:06:00.000Z","6.9.4","5.1","7.2",[52,53,54,55,20],"block-country","block-ip","country-firewall","country-restriction","https:\u002F\u002Fiuliacazan.ro\u002Flogin-ip-country-restriction\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Flogin-ip-country-restriction.6.8.1.zip",100,{"slug":60,"name":60,"version":61,"author":62,"author_profile":63,"description":64,"short_description":65,"active_installs":66,"downloaded":67,"rating":13,"num_ratings":13,"last_updated":68,"tested_up_to":69,"requires_at_least":70,"requires_php":17,"tags":71,"homepage":77,"download_link":78,"security_score":79,"vuln_count":13,"unpatched_count":13,"last_vuln_date":24,"fetched_at":25},"dpabadbotwp","1.27 [20200927]","peter achutha","https:\u002F\u002Fprofiles.wordpress.org\u002Fpeter-achutha\u002F","\u003Cp>The Bad Bot Exterminator Pro is a php program that was developed to block hacker attacks on WordPress websites. Please visit the website at https:\u002F\u002Fwww.drpeterscode.com for more details on the Bad bot Exterminator that blocks hackers, stops brute force login attempts and defends against ddos attacks.\u003C\u002Fp>\n\u003Cp>As of 2018 there are two versions of the Bad Bot Exterminator – the Free Version and the Pro Version which is within the budget of most people. There have been many improvements over the last 5.5 years and is much easier to use. The Free version has been discontinued.\u003C\u002Fp>\n\u003Cp>This plugin, dpabadbotwp works with both the Bad Bot Exterminator Pro & Free versions. The Bad Bot Exterminator is a firewall to protect your WordPress website and is not a plugin but an independent PHP program that runs in parallel with WordPress.\u003C\u002Fp>\n\u003Cp>With the Bad Bot Exterminator\u003Cbr \u002F>\ni. you can lock up your WordPress site so that no one can login to your site.\u003Cbr \u002F>\nii. will track and record every visitor and decides who should be allowed to access your website. It tries to block hackers, bad bots, scrappers, crawlers, spiders, … It can block by IP address or by name of web crawler (in Lenient mode).\u003C\u002Fp>\n\u003Cp>This WordPress plugin, dpaBadBotWP was developed to tell the Bad Bot Exterminator when you are working on your WordPress site and allows you to carry on working by sending your IP address to Bad Bot Exterminator and thereby allowing you unlimited access to your website. By its self this plugin will not be useful if you have not a installed Bad Bot Exterminator.\u003C\u002Fp>\n\u003Cp>It now stops automatic WordPress core updates so that the Bad Bot Exterminator will not be erased.\u003C\u002Fp>\n\u003Cp>Do visit our site https:\u002F\u002Fwww.drpeterscode.com\u002Findex.php for more information on the Bad Bot Exterminator\u003C\u002Fp>\n\u003Ch3>1.01\u003C\u002Fh3>\n\u003Cp>Previous version forgot to check ip address when logged into WordPress control panel. This version corrects that. The moment you are logged in, your current IP address is sent to dpaBadBot.\u003C\u002Fp>\n\u003Ch3>1.02\u003C\u002Fh3>\n\u003Cp>Added a better description of products offered by Software Propulsion with links to respective websites\u003C\u002Fp>\n\u003Ch3>1.03\u003C\u002Fh3>\n\u003Cp>Changed all file names to lower case so that they will be compatible with all servers. If you are upgrading and the plugin has problems accessing files, DELETE this plugin and reinstall the plugin.\u003C\u002Fp>\n\u003Ch3>1.04\u003C\u002Fh3>\n\u003Cp>dpaBadBot PHP program was upgraded to allow you to preview your edited posts. So this plugin had extra security feature added to work with these dpaBadBot upgrades.\u003C\u002Fp>\n\u003Ch3>1.05\u003C\u002Fh3>\n\u003Cp>Removed the check for logout as not a good idea.\u003C\u002Fp>\n\u003Ch3>1.06\u003C\u002Fh3>\n\u003Cp>Changed which ip address is saved. Only latest IP address is saved and all older one’s are deleted.\u003C\u002Fp>\n\u003Ch3>1.07\u003C\u002Fh3>\n\u003Cp>Added multiuser tracking. This version to be used with version 1.06 or later or the Bad Bot Exterminator.\u003C\u002Fp>\n\u003Ch3>1.08\u003C\u002Fh3>\n\u003Cp>Stops automatic WordPress core updates by setting filter ‘auto_update_core’ to ‘__return_false’.\u003C\u002Fp>\n\u003Ch3>1.09\u003C\u002Fh3>\n\u003Cp>Made the PHP code more compatible with the WordPress style by using the debug setting in wp-config.php\u003C\u002Fp>\n\u003Ch3>1.10\u003C\u002Fh3>\n\u003Cp>Corrected some bugs. The directory name can now end with or without ‘\u002F’.\u003C\u002Fp>\n\u003Ch3>1.11\u003C\u002Fh3>\n\u003Cp>Undid some of the upgrades in 1.09 to make it less prone to spurios memory problems.\u003C\u002Fp>\n\u003Ch3>1.12\u003C\u002Fh3>\n\u003Cp>Made some code more compatible with WordPress and checked if file existed.\u003C\u002Fp>\n\u003Ch3>1.13\u003C\u002Fh3>\n\u003Cp>Found out that when you upgrade any plugin, WordPress will delete the existing plugin before downloading the upgrade version. Since this plugin saves all settings in the plugin directory all settings were lost upon upgrading. With version 1.13 a separate directory is created …\u002Fwp-contents\u002Fplugins\u002Fdpabadbotwpdata\u002F and all settings are saved in the altrnative sub-directory. Thus even after upgrading the original seetings are still available.\u003C\u002Fp>\n\u003Cp>Changed all variable names to begin with $spmywp_.\u003C\u002Fp>\n\u003Ch3>1.14\u003C\u002Fh3>\n\u003Cp>changed permission of …\u002Fwp-content\u002Fplugins\u002Fdpabadbotwpdata\u002F sub-directory to 0775 & stop recording visitors not logged in\u003C\u002Fp>\n\u003Ch3>1.15\u003C\u002Fh3>\n\u003Cp>added display of memory in MB too.\u003C\u002Fp>\n\u003Ch3>1.16\u003C\u002Fh3>\n\u003Cp>corrected the link to two other websites.\u003C\u002Fp>\n\u003Ch3>1.17\u003C\u002Fh3>\n\u003Cp>Added display ID and username of those who logged in and moved data directory to \u002Fuploads\u002F directory in line with WordPress standard. As of 2017 March 09, it shows which pages, posts or WP files were accessed. This if for you to look at who logged in and what they did to your copy of WordPress.\u003C\u002Fp>\n\u003Ch3>1.18\u003C\u002Fh3>\n\u003Cp>This plugin now tracks which pages, posts or WP files were accessed. This if for you to look at who logged in and what they did to your copy of WordPress.\u003C\u002Fp>\n\u003Ch3>1.19\u003C\u002Fh3>\n\u003Cp>Version 1.18 had a array assigned wrongly. Its fixed with this version. The table showing who logged and where they went was corrected.\u003C\u002Fp>\n\u003Ch3>1.20\u003C\u002Fh3>\n\u003Cp>Version 1.19 had a searched file name wrong. Its corrected.\u003C\u002Fp>\n\u003Ch3>1.21\u003C\u002Fh3>\n\u003Cp>Removed session start as it was closing the Bad Bot Exterminator when logging out of WordPress. Changed the comments.\u003C\u002Fp>\n\u003Ch3>1.22\u003C\u002Fh3>\n\u003Cp>Tracing of pages added. Removed ‘\u002F’ from data sent to The Bad Bot Exterminator.\u003C\u002Fp>\n\u003Ch3>1.23\u003C\u002Fh3>\n\u003Cp>Tried to improve PHP code speed \u002F effeciency. Declared undefined variables. Added Speed Check for WordPress webpages through the Bad Bot Exterminator Pro. Changed all links to new website at https:\u002F\u002Fwww.drpeterscode.com\u003C\u002Fp>\n\u003Ch3>1.24\u003C\u002Fh3>\n\u003Cp>added .htaccess file to uploads directory\u003C\u002Fp>\n\u003Ch3>1.25\u003C\u002Fh3>\n\u003Cp>added code to generate sitemap data\u003C\u002Fp>\n\u003Ch3>1.26\u003C\u002Fh3>\n\u003Cp>correcter variable name is php shutdown function and improved speed test\u003C\u002Fp>\n\u003Ch3>1.27\u003C\u002Fh3>\n\u003Cp>corrected detection of undefined array\u003C\u002Fp>\n","This plugin, dpaBadBotWP, automatically tells Bad Bot Exterminator firewall software, your current IP address and you will not be blocked from working …",10,3570,"2020-09-27T08:27:00.000Z","5.5.18","3.9.1",[72,73,74,75,76],"bad-bot","block-hackers","brute-force-login","hack","security","https:\u002F\u002Fwww.drpeterscode.com\u002Fbad-bot-exterminator-protects-wordpress-sites-from-hackers-cyber-ddos-dos-attacks.php","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdpabadbotwp.zip",85,{"slug":81,"name":82,"version":83,"author":84,"author_profile":85,"description":86,"short_description":87,"active_installs":66,"downloaded":88,"rating":58,"num_ratings":89,"last_updated":90,"tested_up_to":91,"requires_at_least":92,"requires_php":17,"tags":93,"homepage":17,"download_link":98,"security_score":79,"vuln_count":13,"unpatched_count":13,"last_vuln_date":24,"fetched_at":25},"login-mandatory-pages","Login Mandatory Pages","1.2","dinesh224","https:\u002F\u002Fprofiles.wordpress.org\u002Fdinesh224\u002F","\u003Cp>Login Mandatory pages is a good handy and free solution for everyone who is looking to convert their simple pages to only accessible for logged in user.\u003Cbr \u002F>\nIt also provides setting to users to modify text on selected pages and also users can set their “login” page link.\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>\u003Cstrong>Login Mandatory pages\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Easy to install\u003C\u002Fli>\n\u003Cli>Select the pages which you want to inaccessible for guest users\u003C\u002Fli>\n\u003Cli>You can set message on selected pages.\u003C\u002Fli>\n\u003Cli>You can also add a link of your website’s login page.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fblockquote>\n","Login Mandatory pages is a WordPress plugin that allows you to make pages accessible for only logged in users.",1302,1,"2017-10-04T11:21:00.000Z","4.8.28","4.0",[94,19,95,96,97],"control-pages","login-page","login-pages","user-access-control","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Flogin-mandatory-pages.1.2.zip",{"slug":100,"name":101,"version":102,"author":103,"author_profile":104,"description":105,"short_description":106,"active_installs":13,"downloaded":107,"rating":13,"num_ratings":13,"last_updated":108,"tested_up_to":48,"requires_at_least":109,"requires_php":110,"tags":111,"homepage":115,"download_link":116,"security_score":58,"vuln_count":13,"unpatched_count":13,"last_vuln_date":24,"fetched_at":25},"absoluto-access-gate","Absoluto Access Gate","1.0.0","Absoluto Designs","https:\u002F\u002Fprofiles.wordpress.org\u002Fabsolutodesigns\u002F","\u003Cp>Absoluto Access Gate is a flexible WordPress access-control plugin that allows you to require user login across your site while offering precise control over who can access what. It is designed for site owners who need reliable login enforcement without sacrificing usability or performance.\u003C\u002Fp>\n\u003Cp>Many sites require authentication for content access but still need exceptions for specific pages, users, or integrations. Absoluto Access Gate provides a structured and predictable way to enforce login rules while supporting common real-world scenarios such as public landing pages, APIs, feeds, and temporary access needs.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Author:\u003C\u002Fstrong> Absoluto Designs\u003Cbr \u002F>\n\u003Cstrong>Author URI:\u003C\u002Fstrong> http:\u002F\u002Fabsolutodesigns.com\u003Cbr \u002F>\n\u003Cstrong>Plugin URI:\u003C\u002Fstrong> https:\u002F\u002Fabsolutodesigns.com\u002Fplugins\u002Fabsoluto-access-gate\u002F\u003C\u002Fp>\n\u003Ch3>Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Force login requirement for all pages\u003C\u002Fli>\n\u003Cli>Enable\u002FDisable toggle without deactivating plugin\u003C\u002Fli>\n\u003Cli>Exclude specific pages from login requirement\u003C\u002Fli>\n\u003Cli>Exclude page templates from login requirement\u003C\u002Fli>\n\u003Cli>Exclude post types, categories, and tags\u003C\u002Fli>\n\u003Cli>Allow specific user roles to bypass login requirement\u003C\u002Fli>\n\u003Cli>Allow specific users to bypass login requirement\u003C\u002Fli>\n\u003Cli>IP whitelist with CIDR notation support\u003C\u002Fli>\n\u003Cli>Bypass key\u002Ftoken for temporary access\u003C\u002Fli>\n\u003Cli>Custom login page URL\u003C\u002Fli>\n\u003Cli>Custom redirect after login\u003C\u002Fli>\n\u003Cli>Maintenance mode with custom messages\u003C\u002Fli>\n\u003Cli>RSS feed and REST API exclusion options\u003C\u002Fli>\n\u003Cli>AJAX request exclusion\u003C\u002Fli>\n\u003Cli>Archive and search page exclusion\u003C\u002Fli>\n\u003Cli>Easy-to-use admin settings page with 2-column layout\u003C\u002Fli>\n\u003Cli>Clean and modern UI with enhanced multi-select dropdowns (uses native HTML5 selects, WordPress.org compliant)\u003C\u002Fli>\n\u003Cli>Quick add current IP to whitelist button\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Configuration\u003C\u002Fh3>\n\u003Cp>After activating the plugin, navigate to \u003Cstrong>Settings > Absoluto Access Gate\u003C\u002Fstrong> to configure:\u003C\u002Fp>\n\u003Ch3>Excluded Pages\u003C\u002Fh3>\n\u003Cp>Select pages that should be accessible without login. These pages will be publicly accessible even when the plugin is active.\u003C\u002Fp>\n\u003Ch3>Excluded Page Templates\u003C\u002Fh3>\n\u003Cp>Select page templates that should be accessible without login. All pages using these templates will be publicly accessible.\u003C\u002Fp>\n\u003Ch3>Bypass Roles\u003C\u002Fh3>\n\u003Cp>Select user roles that can bypass the login requirement. Users with these roles can view all pages without being redirected to login.\u003C\u002Fp>\n\u003Ch3>Bypass Users\u003C\u002Fh3>\n\u003Cp>Select specific users that can bypass the login requirement. These users can view all pages without being redirected to login.\u003C\u002Fp>\n\u003Ch3>How It Works\u003C\u002Fh3>\n\u003Col>\n\u003Cli>\n\u003Cp>When a user visits any page on your site, the plugin checks:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>If the user is logged in and has bypass permission (role or user)\u003C\u002Fli>\n\u003Cli>If the current page is excluded\u003C\u002Fli>\n\u003Cli>If the current page uses an excluded template\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>If none of the above conditions are met and the user is not logged in, they are redirected to the WordPress login page.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>After logging in, users are redirected back to the page they were trying to access.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>Requirements\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>WordPress:\u003C\u002Fstrong> 5.0 or higher\u003C\u002Fli>\n\u003Cli>\u003Cstrong>PHP:\u003C\u002Fstrong> 7.0 or higher\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Tested up to:\u003C\u002Fstrong> WordPress 6.4\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Network:\u003C\u002Fstrong> Not compatible with WordPress Multisite network activation\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Support\u003C\u002Fh3>\n\u003Cp>For issues, questions, or contributions, please visit the \u003Ca href=\"https:\u002F\u002Fabsolutodesigns.com\u002Fplugins\u002Fabsoluto-access-gate\u002F\" rel=\"nofollow ugc\">plugin page\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>License\u003C\u002Fh3>\n\u003Cp>GPL v2 or later\u003C\u002Fp>\n","Force users to login before viewing pages. Exclude specific pages and allow certain user roles\u002Fusers to bypass the requirement.",123,"2026-01-27T10:51:00.000Z","5.0","7.0",[112,19,113,114,76],"access-control","login","restrict-access","https:\u002F\u002Fabsolutodesigns.com\u002Fplugins\u002Fabsoluto-access-gate\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fabsoluto-access-gate.1.0.0.zip",{"attackSurface":118,"codeSignals":155,"taintFlows":173,"riskAssessment":174,"analyzedAt":185},{"hooks":119,"ajaxHandlers":151,"restRoutes":152,"shortcodes":153,"cronEvents":154,"entryPointCount":13,"unprotectedCount":13},[120,126,131,135,139,143,147],{"type":121,"name":122,"callback":123,"file":124,"line":125},"filter","pre_set_site_transient_update_plugins","updateForceLogin","force-user-login-by-webline.php",32,{"type":127,"name":128,"callback":129,"file":124,"line":130},"action","admin_enqueue_scripts","fl_enqueue_scripts",66,{"type":127,"name":132,"callback":133,"file":124,"line":134},"admin_menu","addForceLoginMenu",67,{"type":127,"name":136,"callback":137,"file":124,"line":138},"admin_init","plugin_admin_init",68,{"type":121,"name":140,"callback":141,"file":124,"line":142},"admin_footer_text","flbw_admin_footer",152,{"type":127,"name":144,"callback":145,"file":124,"line":146},"init","forceLogin",234,{"type":121,"name":148,"callback":149,"priority":66,"file":124,"line":150},"login_redirect","my_login_redirect",235,[],[],[],[],{"dangerousFunctions":156,"sqlUsage":157,"outputEscaping":159,"fileOperations":13,"externalRequests":13,"nonceChecks":13,"capabilityChecks":13,"bundledLibraries":172},[],{"prepared":13,"raw":13,"locations":158},[],{"escaped":160,"rawEcho":161,"locations":162},2,4,[163,166,168,170],{"file":124,"line":164,"context":165},172,"raw output",{"file":124,"line":167,"context":165},187,{"file":124,"line":169,"context":165},190,{"file":124,"line":171,"context":165},193,[],[],{"summary":175,"deductions":176},"The plugin \"force-user-login-by-webline\" v1.0.10 exhibits a strong security posture based on the provided static analysis. The absence of AJAX handlers, REST API routes, shortcodes, and cron events significantly limits the attack surface, with no identified entry points, protected or otherwise. The code also demonstrates good practices by avoiding dangerous functions, file operations, and external HTTP requests. All SQL queries are correctly implemented using prepared statements, mitigating SQL injection risks. The plugin also has a clean vulnerability history, with no known CVEs, suggesting a history of secure development and maintenance. \n\nDespite these strengths, there are areas for improvement. The output escaping is only properly handled for 33% of outputs, leaving 67% potentially vulnerable to Cross-Site Scripting (XSS) attacks if user-supplied data is directly reflected. Furthermore, the complete lack of nonce checks and capability checks across all entry points (though currently zero) is a concern. If any new entry points are introduced in future versions without these security measures, the plugin would become highly vulnerable to various attacks, including CSRF and unauthorized privilege escalation. The absence of taint analysis flows also prevents a complete understanding of data sanitization effectiveness for any potential future data handling.",[177,180,183],{"reason":178,"points":179},"Low output escaping coverage",6,{"reason":181,"points":182},"No nonce checks implemented",5,{"reason":184,"points":182},"No capability checks implemented","2026-03-16T22:14:46.535Z",{"wat":187,"direct":196},{"assetPaths":188,"generatorPatterns":191,"scriptPaths":192,"versionParams":193},[189,190],"\u002Fwp-content\u002Fplugins\u002Fforce-user-login-by-webline\u002Fcss\u002Fflbw-admin-notices.css","\u002Fwp-content\u002Fplugins\u002Fforce-user-login-by-webline\u002Fjs\u002Finstall_plugin_flbw.js",[],[190],[194,195],"force-user-login-by-webline\u002Fcss\u002Fflbw-admin-notices.css?ver=","force-user-login-by-webline\u002Fjs\u002Finstall_plugin_flbw.js?ver=",{"cssClasses":197,"htmlComments":207,"htmlAttributes":208,"restEndpoints":211,"jsGlobals":212,"shortcodeOutput":213},[198,199,200,201,202,203,204,205,206],"flbw-plugin-cta","flbw-heading","custom-bullet","show-other-plugin","wrap-flbw","inner-flbw","left-box-flbw","right-box-flbw","button-install",[],[209,210],"id='xml-plugin-banner'","id='open-install-flbw'",[],[],[]]