[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fTEvUUdxsIlwyrCNHC4UKYO4FRDi4xvmx-pQIDsLprMY":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":14,"last_updated":15,"tested_up_to":16,"requires_at_least":17,"requires_php":18,"tags":19,"homepage":23,"download_link":24,"security_score":25,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28,"vulnerabilities":29,"developer":30,"crawl_stats":27,"alternatives":37,"analysis":130,"fingerprints":205},"comment-blacklist-manager","Comment Blacklist Manager","1.0.1","Andrew Norcross","https:\u002F\u002Fprofiles.wordpress.org\u002Fnorcross\u002F","\u003Cp>Comment Blacklist Manager retrieves a list of terms from a remote source and updates the \u003Ccode>disallowed_keys\u003C\u002Fcode> setting in WordPress. The plugin will automatically fetch a list of terms on a regular schedule and update the contents of the “Disallowed Comment Keys” field. Terms added manually via the “Local Blacklist” field will be retained during the scheduled updates. Terms added manually to the “Excluded Terms” field will be removed from the list.\u003C\u002Fp>\n\u003Cp>The default list of terms is fetched from a \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fsplorp\u002Fwordpress-comment-blacklist\u002F\" title=\"Comment Blacklist for WordPress\" rel=\"nofollow ugc\">GitHub\u003C\u002Fa> repository maintained by \u003Ca href=\"https:\u002F\u002Fsplorp.com\u002F\" title=\"Interface considerations. Gadget accumulation. Typography. Scotch.\" rel=\"nofollow ugc\">Grant Hutchinson\u003C\u002Fa>.\u003C\u002Fp>\n","Remotely add terms to the WordPress Disallowed Comment Keys field to manage spam.",600,8186,88,5,"2025-12-13T21:44:00.000Z","6.9.4","5.6","7.0",[20,21,22],"blacklist","comments","spam","https:\u002F\u002Fgithub.com\u002Fnorcross\u002Fcomment-blacklist-manager","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcomment-blacklist-manager.1.0.1.zip",100,0,null,"2026-03-15T15:16:48.613Z",[],{"slug":31,"display_name":7,"profile_url":8,"plugin_count":32,"total_installs":33,"avg_security_score":13,"avg_patch_time_days":34,"trust_score":35,"computed_at":36},"norcross",18,2120,30,86,"2026-04-04T07:04:24.942Z",[38,57,79,98,114],{"slug":39,"name":40,"version":41,"author":42,"author_profile":43,"description":44,"short_description":45,"active_installs":46,"downloaded":47,"rating":35,"num_ratings":48,"last_updated":49,"tested_up_to":16,"requires_at_least":50,"requires_php":51,"tags":52,"homepage":55,"download_link":56,"security_score":25,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"blacklist-updater","Block List Updater","1.0.2","pluginkollektiv","https:\u002F\u002Fprofiles.wordpress.org\u002Fpluginkollektiv\u002F","\u003Cp>Few users are familiar with the comment block list built into WordPress. Located in the WordPress admin area under “Settings”—“Discussion”, that block list for incoming comments accepts values (words) to identify spam by.\u003C\u002Fp>\n\u003Cp>Additionally to plugins like \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fantispam-bee\u002F\" rel=\"ugc\">Antispam Bee\u003C\u002Fa> in order to fight spam successfully a curated comment block list is recommendable. You can either update the list manually, or utilize a very detailed global \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fsplorp\u002Fwordpress-comment-blacklist\" rel=\"nofollow ugc\">comment block list\u003C\u002Fa> that gets updated on a regular basis.\u003C\u002Fp>\n\u003Cp>Block List Updater has been developed to keep your comment block list in your WordPress installation up to speed with the curated global list on GitHub.\u003C\u002Fp>\n\u003Cp>The plugin will check the global comment block list on GitHub multiple times a day. Whenever new anti-spam values have been added to the global list, Block List Updater will read the global list and update your WordPress database accordingly. While the check-up process will run several times a day, the plugin will only update the database when it detects an actual change of the global comment block list on GitHub.\u003C\u002Fp>\n\u003Ch3>Support\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Community support via the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fblacklist-updater\" rel=\"ugc\">support forums on wordpress.org\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>We don’t handle support via e-mail, Twitter, GitHub issues etc.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Contribute\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Active development of this plugin is handled \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fpluginkollektiv\u002Fblacklist-updater\" rel=\"nofollow ugc\">on GitHub\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>Pull requests for documented bugs are highly appreciated.\u003C\u002Fli>\n\u003Cli>If you think you’ve found a bug (e.g. you’re experiencing unexpected behavior), please post at the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fblacklist-updater\" rel=\"ugc\">support forums\u003C\u002Fa> first.\u003C\u002Fli>\n\u003Cli>If you want to help us translate this plugin you can do so \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Fprojects\u002Fwp-plugins\u002Fblacklist-updater\" rel=\"nofollow ugc\">on WordPress Translate\u003C\u002Fa>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Credits\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Author: \u003Ca href=\"https:\u002F\u002Fsergejmueller.github.io\u002F\" rel=\"nofollow ugc\">Sergej Müller\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Maintainers: \u003Ca href=\"https:\u002F\u002Fpluginkollektiv.org\u002F\" rel=\"nofollow ugc\">pluginkollektiv\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n","Automatic updating of the comment block list in WordPress with antispam keys from GitHub.",4000,31272,4,"2026-03-14T09:16:00.000Z","3.8","5.2",[53,20,54,21,22],"antispam","blocklist","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fblacklist-updater\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fblacklist-updater.1.0.2.zip",{"slug":58,"name":59,"version":60,"author":61,"author_profile":62,"description":63,"short_description":64,"active_installs":65,"downloaded":66,"rating":67,"num_ratings":48,"last_updated":68,"tested_up_to":69,"requires_at_least":70,"requires_php":17,"tags":71,"homepage":74,"download_link":75,"security_score":76,"vuln_count":77,"unpatched_count":26,"last_vuln_date":78,"fetched_at":28},"comment-blacklist-updater","Comment Blacklist Updater","1.2.2","apasionados","https:\u002F\u002Fprofiles.wordpress.org\u002Fapasionados\u002F","\u003Cp>Updates the “Comment Blacklist” in Settings \u002F Discussion with a list terms from a remote or local source. By default it get’s the data from Github \u003Cstrong>(“\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fsplorp\u002Fwordpress-comment-blacklist\u002F\" rel=\"nofollow ugc\">wordpress-comment-blacklist\u003C\u002Fa>“)\u003C\u002Fstrong> by \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fsplorp\" rel=\"nofollow ugc\">Grant Hutchinson\u003C\u002Fa>) but you can also get them \u003Cstrong>from any URL\u003C\u002Fstrong> or from a \u003Cstrong>local blacklist.txt file\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>This plugin is an enhanced version of the plugin \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fcomment-blacklist-manager\u002F\" rel=\"ugc\">Comment Blacklist Manager\u003C\u002Fa>. We decided to create this enhanced version of the plugin, because we wanted to be able to add blacklists without using filters and directly from the WordPress administration. You can still use a filter to modify the blacklist sources if that is more convienient for you. And we also wanted to have more information about the plugin in SETTINGS \u002F DISCUSSION; for example when the blacklist was updated and when it will be updated next time, when the blacklist sources were updated, etc.\u003C\u002Fp>\n\u003Cp>You can configure three sources for your blacklists:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Default blacklist\u003C\u002Fstrong> (which can be disabled): \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fsplorp\u002Fwordpress-comment-blacklist\u002F\" rel=\"nofollow ugc\">wordpress-comment-blacklist\u003C\u002Fa> by \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fsplorp\" rel=\"nofollow ugc\">Grant Hutchinson\u003C\u002Fa>). Please keep in mind that if there is no other blacklist source defined, this will be used as default, even if it\\’s not selected.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Blacklist from remote URL\u003C\u002Fstrong>: You paste the URL to the blacklist and if the file exists and can be accesed (must return code 200) it will be used as a blacklist source.\u003C\u002Fli>\n\u003Cli>If you want to include a \u003Cstrong>local blacklist\u003C\u002Fstrong> for the site, you can upload a blacklist.txt file to the UPLOADS folder and it will also be taken into account. The blacklist.txt file has to be in the root of the UPLOADS folder; it will not be recognized if it\\’s for example in \u002Fuploads\u002F2025\u002F12\u002F and the file has to be accesible via http\u002Fhttps (if the access to the file is protected it can\\’t be used).\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>And you can use the filter \u003Ccode>cblm_sources\u003C\u002Fcode> to replace all the blacklists or to add more. If you replace all blacklists with the filter, the settings done in the WordPress administration will be ignored. We decided to keep the same filter as used by “Comment Blacklist Manager” to make it easy to switch between both plugins.\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>Please note: \u003Cstrong>After the September 2023 update only users with administrator privileges can use this plugin.\u003C\u002Fstrong> If you’re not an admin you will get following error: “You do not have sufficient permissions to access this page”.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch4>What can I do with this plugin?\u003C\u002Fh4>\n\u003Cp>The plugin updates the “Comment Blacklist” in Settings \u002F Discussion with a list terms from a remote or local source. By default it get’s the data from Github (“\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fsplorp\u002Fwordpress-comment-blacklist\u002F\" rel=\"nofollow ugc\">wordpress-comment-blacklist\u003C\u002Fa> by \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fsplorp\" rel=\"nofollow ugc\">Grant Hutchinson\u003C\u002Fa>) but you can also get them from any URL or from a local blacklist.txt file.\u003C\u002Fp>\n\u003Ch4>Why do I want to update the “Comment Blacklist” in Settings \u002F Discussion?\u003C\u002Fh4>\n\u003Cp>If you want to reduce spam received in your comment forms but also in your contact forms (for example when using Contact Form 7), using blacklisted terms can help.\u003C\u002Fp>\n\u003Cp>Contact Form 7 encourages to use: Akismet, reCaptcha and the comment blacklist to reduce contact form spam.\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>\u003Cem>Contact Form 7 supports spam-filtering with Akismet. Intelligent reCAPTCHA blocks annoying spambots. Plus, using comment blacklist, you can block messages containing specified keywords or those sent from specified IP addresses.\u003C\u002Fem>\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>The best way to reduce the contact form 7 spam is to use a very extensive term database which is updated regulary with new spam terms. And this plugin does exactly this: Updating the blacklist regularly.\u003C\u002Fp>\n\u003Ch4>Why are you using the “Comment Blacklist for WordPress” from Grant Hutchinson as default source for the blacklist?\u003C\u002Fh4>\n\u003Cp>Since 2011 Grant Hutchinson has been identifying and compiling over 34,000 phrases, patterns, and keywords commonly used by spammers and comment bots in usernames, email addresses, link text, and URIs.\u003C\u002Fp>\n\u003Cp>His blacklist is very extensive and that’s why we love it.\u003C\u002Fp>\n\u003Cp>As with all compilations, this blacklist is a work in progress and it is updated more or less every month. And each of these updates will be included automatically with the update process that runs every 24 hours.\u003C\u002Fp>\n\u003Cp>\u003Cem>Sometimes simple is better.\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>If you know another source that is as extensive as this one, drop us a message and we will check if it’s interesting to add it also as a default.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch4>System requirements\u003C\u002Fh4>\n\u003Cp>PHP version 5.6 or greater.\u003C\u002Fp>\n\u003Ch4>Comment Blacklist Updater Plugin in your Language!\u003C\u002Fh4>\n\u003Cp>This first release is avaliable in English and Spanish. In the “languages” folder we have included the necessary files to translate this plugin.\u003C\u002Fp>\n\u003Cp>If you would like the plugin in your language and you’re good at translating, please drop us a line at \u003Ca href=\"https:\u002F\u002Fapasionados.es\u002Fcontacto\u002Findex.php?desde=wordpress-org-apa-comment-blacklist-updater-home\" rel=\"nofollow ugc\">Contact us\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch4>Further Reading\u003C\u002Fh4>\n\u003Cp>You can access the description of the plugin in Spanish at: \u003Ca href=\"https:\u002F\u002Fapasionados.es\u002Fblog\u002F\" rel=\"nofollow ugc\">Actualizador lista negra de comentarios | WordPress Plugin\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Contact\u003C\u002Fh3>\n\u003Cp>For further information please send us an \u003Ca href=\"https:\u002F\u002Fapasionados.es\u002Fcontacto\u002Findex.php?desde=wordpress-org-apa-comment-blacklist-updater\" rel=\"nofollow ugc\">email\u003C\u002Fa>.\u003C\u002Fp>\n","Update \"Comment Blacklist\" spam terms to manage spam in forms and comments",1000,10162,96,"2023-09-26T13:22:00.000Z","6.3.8","4.0.1",[20,21,72,73,22],"contact-form-7","form-spam","https:\u002F\u002Fapasionados.es\u002Fblog\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcomment-blacklist-updater.1.2.2.zip",85,1,"2023-09-23 00:00:00",{"slug":80,"name":81,"version":82,"author":83,"author_profile":84,"description":85,"short_description":86,"active_installs":87,"downloaded":88,"rating":26,"num_ratings":26,"last_updated":89,"tested_up_to":90,"requires_at_least":91,"requires_php":89,"tags":92,"homepage":95,"download_link":96,"security_score":25,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":97},"back-list","Back List","0.5","w3prodigy","https:\u002F\u002Fprofiles.wordpress.org\u002Fw3prodigy\u002F","\u003Cp>Adds Whitelist and Blacklist options for Trackbacks and Pingbacks as well as the option to auto-accept Trackbacks from your own blog. These options can be found on the Discussion Options page.\u003C\u002Fp>\n","Adds Whitelist and Blacklist options for Trackbacks and Pingbacks",10,2230,"","3.0.5","3.0",[93,20,21,94],"anti-spam","security","http:\u002F\u002Fw3prodigy.com\u002Fwordpress-plugins\u002Fback-list\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fback-list.zip","2026-03-15T10:48:56.248Z",{"slug":99,"name":100,"version":101,"author":102,"author_profile":103,"description":104,"short_description":105,"active_installs":87,"downloaded":106,"rating":26,"num_ratings":26,"last_updated":107,"tested_up_to":108,"requires_at_least":109,"requires_php":89,"tags":110,"homepage":112,"download_link":113,"security_score":76,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"wp-mail-validator","WP-Mail-Validator","0.6.5","kimpenhaus","https:\u002F\u002Fprofiles.wordpress.org\u002Fkimpenhaus\u002F","\u003Cp>WP-Mail-Validator is an anti-spam plugin. It provides mail-address validation in 5 ways:\u003C\u002Fp>\n\u003Col>\n\u003Cli>syntax of mail-addresses\u003C\u002Fli>\n\u003Cli>mailserver host\u003C\u002Fli>\n\u003Cli>mx-record of mailserver\u003C\u002Fli>\n\u003Cli>user-defined blacklist\u003C\u002Fli>\n\u003Cli>trashmail services\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Once the plugin identifies a mail-address to be non existing on the mailserver or being on the blacklist or\u003Cbr \u002F>\nfrom trashmail service, any comment being made is moved to the spam area awaiting moderation from the blog owner.\u003C\u002Fp>\n\u003Ch3>Theme-Modification\u003C\u002Fh3>\n\u003Cp>WP-Mail-Validator comes with 3 theme functions that can be used:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Ccode>wp_mail_validator_info_label()\u003C\u002Fcode>: shows a protected by info label\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp_mail_validator_version()\u003C\u002Fcode>: shows the current plugin version\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp_mail_validator_fended_spam_attack_count()\u003C\u002Fcode>: shows the count of spam attackes fended\u003C\u002Fli>\n\u003C\u002Fol>\n","WP-Mail-Validator is an anti-spam plugin. It provides mail-address validation in 5 ways:",3191,"2020-04-13T17:37:00.000Z","5.4.19","5.2.0",[93,20,21,94,111],"trashmail","https:\u002F\u002Fgithub.com\u002Fkimpenhaus\u002Fwp-mail-validator","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-mail-validator.0.6.5.zip",{"slug":115,"name":116,"version":117,"author":118,"author_profile":119,"description":120,"short_description":121,"active_installs":26,"downloaded":122,"rating":26,"num_ratings":26,"last_updated":89,"tested_up_to":123,"requires_at_least":124,"requires_php":89,"tags":125,"homepage":128,"download_link":129,"security_score":25,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":97},"spam-to-blacklist","Spam to blacklist","1.0","proninyaroslav","https:\u002F\u002Fprofiles.wordpress.org\u002Fproninyaroslav\u002F","\u003Cp>Adds IP from comment that marked as spam to standard WordPress blacklist. Comments already marked as spam are not added to the list.\u003C\u002Fp>\n","Adds IP from comment that marked as spam to standard WordPress blacklist.",1133,"4.9.29","4.9",[126,20,21,127,22],"ban","ip","https:\u002F\u002Fgithub.com\u002Fproninyaroslav\u002Fspam-to-blacklist","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fspam-to-blacklist.1.0.zip",{"attackSurface":131,"codeSignals":162,"taintFlows":191,"riskAssessment":192,"analyzedAt":204},{"hooks":132,"ajaxHandlers":158,"restRoutes":159,"shortcodes":160,"cronEvents":161,"entryPointCount":26,"unprotectedCount":26},[133,139,143,146,149,153],{"type":134,"name":135,"callback":136,"file":137,"line":138},"action","plugins_loaded","textdomain","comment-blacklist-manager.php",42,{"type":134,"name":140,"callback":141,"file":137,"line":142},"admin_init","load_settings",43,{"type":134,"name":140,"callback":144,"file":137,"line":145},"update_blacklist_admin",44,{"type":134,"name":140,"callback":147,"file":137,"line":148},"update_blacklist_manual",45,{"type":134,"name":150,"callback":151,"file":137,"line":152},"admin_notices","manual_update_notice",46,{"type":154,"name":155,"callback":156,"file":137,"line":157},"filter","removable_query_args","add_removable_args",47,[],[],[],[],{"dangerousFunctions":163,"sqlUsage":164,"outputEscaping":166,"fileOperations":26,"externalRequests":77,"nonceChecks":26,"capabilityChecks":26,"bundledLibraries":190},[],{"prepared":26,"raw":26,"locations":165},[],{"escaped":167,"rawEcho":87,"locations":168},6,[169,172,174,176,178,180,182,184,186,188],{"file":137,"line":170,"context":171},148,"raw output",{"file":137,"line":173,"context":171},152,{"file":137,"line":175,"context":171},160,{"file":137,"line":177,"context":171},167,{"file":137,"line":179,"context":171},174,{"file":137,"line":181,"context":171},188,{"file":137,"line":183,"context":171},192,{"file":137,"line":185,"context":171},209,{"file":137,"line":187,"context":171},213,{"file":137,"line":189,"context":171},284,[],[],{"summary":193,"deductions":194},"The \"comment-blacklist-manager\" plugin v1.0.1 exhibits a generally good security posture based on the provided static analysis.  The absence of AJAX handlers, REST API routes, shortcodes, cron events, dangerous functions, and file operations significantly limits the potential attack surface.  Furthermore, the plugin exclusively uses prepared statements for SQL queries, a strong indicator of secure database interaction.  The vulnerability history being completely clear further supports a perception of stability. \n\nHowever, there are areas of concern that prevent a perfect score. The most significant is the low percentage (38%) of properly escaped output, suggesting a risk of cross-site scripting (XSS) vulnerabilities if user-supplied data is not handled carefully before being displayed.  The presence of an external HTTP request, while not inherently a vulnerability, is a potential entry point for vulnerabilities if the external resource is compromised or the request is not properly validated.  The lack of nonce checks and capability checks, while mitigated by the absence of unprotected entry points in this specific version, indicates a reliance on the fact that there are no entry points to protect, rather than a robust implementation of security measures that could be exploited if new entry points were added in the future. \n\nIn conclusion, this plugin demonstrates good practices in many critical security areas, particularly concerning database interactions and attack surface minimization.  The clean vulnerability history is a positive sign.  However, the insufficient output escaping and the potential risks associated with external HTTP requests warrant attention. The absence of authorization checks on the limited entry points is a technicality of this version, but a weakness in the underlying architectural design if the plugin were to evolve.",[195,197,200,202],{"reason":196,"points":167},"Insufficient output escaping",{"reason":198,"points":199},"External HTTP requests present",2,{"reason":201,"points":14},"No nonce checks",{"reason":203,"points":14},"No capability checks","2026-03-16T19:30:47.817Z",{"wat":206,"direct":213},{"assetPaths":207,"generatorPatterns":209,"scriptPaths":210,"versionParams":211},[208],"\u002Fwp-content\u002Fplugins\u002Fcomment-blacklist-manager\u002Fcss\u002Fstyle.css",[],[],[212],"comment-blacklist-manager\u002Fcss\u002Fstyle.css?ver=",{"cssClasses":214,"htmlComments":216,"htmlAttributes":217,"restEndpoints":219,"jsGlobals":220,"shortcodeOutput":221},[215],"cblm-update-manual",[],[218],"data-cblm-update",[],[],[]]