[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fAMSCksLrQLzpXHZ3OFVKWpRGJdP8NgQYw7DLUY1c07U":3,"$f9w1OJ01XoP7q8DIsyhXktqX14BiDiiKP0v8k509HAnY":93,"$fV5-etf-Ws7_g2f5QImtQu9s3XEff42chwmZ68Ai43kM":98},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":11,"num_ratings":11,"last_updated":13,"tested_up_to":14,"requires_at_least":15,"requires_php":16,"tags":17,"homepage":18,"download_link":19,"security_score":20,"vuln_count":11,"unpatched_count":11,"last_vuln_date":21,"fetched_at":22,"discovery_status":23,"vulnerabilities":24,"developer":25,"crawl_stats":21,"alternatives":33,"analysis":34,"fingerprints":76},"wooguten-block-editor-for-woocommerce","WooGuten – Block Editor for WooCommerce","0.9.0","Plugin Devs","https:\u002F\u002Fprofiles.wordpress.org\u002Fplugindevs\u002F","\u003Cp>Use Gutenberg Editor for WooCommerce Products. By default Woocommerce is not using gutenberg editor. You can use the Gutenberg Editor and all of its functionalities using this plugin\u003C\u002Fp>\n","Use Gutenberg Editor for WooCommerce Products. By default Woocommerce is not using gutenberg editor. You can use the Gutenberg Editor and all of its f …",0,855,"2020-04-22T20:36:00.000Z","5.3.21","5.0","5.5",[4],"#","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwooguten-block-editor-for-woocommerce.zip",85,null,"2026-04-16T10:56:18.058Z","no_bundle",[],{"slug":26,"display_name":7,"profile_url":8,"plugin_count":27,"total_installs":28,"avg_security_score":29,"avg_patch_time_days":30,"trust_score":31,"computed_at":32},"plugindevs",16,18260,83,60,76,"2026-05-20T02:21:52.995Z",[],{"attackSurface":35,"codeSignals":61,"taintFlows":68,"riskAssessment":69,"analyzedAt":75},{"hooks":36,"ajaxHandlers":57,"restRoutes":58,"shortcodes":59,"cronEvents":60,"entryPointCount":11,"unprotectedCount":11},[37,44,50,54],{"type":38,"name":39,"callback":40,"priority":41,"file":42,"line":43},"filter","use_block_editor_for_post_type","wcge_activate_gutenberg_products",99,"gutenberg-editor-for-woocommerce.php",26,{"type":45,"name":46,"callback":47,"priority":48,"file":42,"line":49},"action","admin_enqueue_scripts","wcge_admin_scripts",10,28,{"type":38,"name":51,"callback":52,"file":42,"line":53},"woocommerce_taxonomy_args_product_cat","wcge_product_cat_allow_rest",30,{"type":38,"name":55,"callback":52,"file":42,"line":56},"woocommerce_taxonomy_args_product_tag",31,[],[],[],[],{"dangerousFunctions":62,"sqlUsage":63,"outputEscaping":65,"fileOperations":11,"externalRequests":11,"nonceChecks":11,"capabilityChecks":11,"bundledLibraries":67},[],{"prepared":11,"raw":11,"locations":64},[],{"escaped":11,"rawEcho":11,"locations":66},[],[],[],{"summary":70,"deductions":71},"This plugin exhibits an excellent security posture based on the provided static analysis.  The absence of any identified dangerous functions, unescaped output, file operations, external HTTP requests, and the strict adherence to prepared statements for SQL queries are strong indicators of secure coding practices.  Furthermore, the lack of any recorded vulnerabilities, past or present, suggests a history of responsible development and maintenance.\n\nThe static analysis reveals a remarkably small attack surface, with zero entry points and no unprotected handlers or routes. This significantly reduces the potential for exploitation. Taint analysis also shows no identified flows, further bolstering the plugin's security. However, the complete absence of nonce and capability checks across all identified (or rather, not identified) entry points could be a cause for concern if the plugin were to evolve and introduce such features without proper authorization mechanisms.  While the current state is secure due to the lack of entry points, this is a potential weakness that should be monitored if the plugin's functionality expands.\n\nOverall, wooguten-block-editor-for-woocommerce v0.9.0 appears to be a highly secure plugin. Its development team has demonstrated a commitment to secure coding practices, and its vulnerability history is clean. The minimal attack surface is a significant strength. The only area for potential future concern is the lack of explicit authorization checks, which is currently mitigated by the plugin's lack of exploitable entry points.",[72],{"reason":73,"points":74},"Lack of nonce and capability checks on entry points",5,"2026-03-17T06:28:28.100Z",{"wat":77,"direct":84},{"assetPaths":78,"generatorPatterns":80,"scriptPaths":81,"versionParams":82},[79],"\u002Fwp-content\u002Fplugins\u002Fwooguten-block-editor-for-woocommerce\u002Fassets\u002Fjs\u002Fadmin.js",[],[],[83],"wcge_admin_script?ver=",{"cssClasses":85,"htmlComments":86,"htmlAttributes":87,"restEndpoints":88,"jsGlobals":90,"shortcodeOutput":92},[],[],[],[89],"\u002Fwp-json\u002Fwc-gutenberg\u002Fv1\u002Fsettings",[91],"wcge_admin_script",[],{"error":94,"url":95,"statusCode":96,"statusMessage":97,"message":97},true,"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Fwooguten-block-editor-for-woocommerce\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":11,"versions":99},[]]