[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fdGZuAdBGaKSy2Sb9w3z0l6EeGbFWttdpdU__fhDdD2o":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":20,"download_link":21,"security_score":22,"vuln_count":23,"unpatched_count":23,"last_vuln_date":24,"fetched_at":25,"vulnerabilities":26,"developer":27,"crawl_stats":24,"alternatives":35,"analysis":36,"fingerprints":66},"edit-image-thumbnails-separately","Edit Image Thumbnails Separately","1.0.0","WordPress.org","https:\u002F\u002Fprofiles.wordpress.org\u002Fwordpressdotorg\u002F","\u003Cp>Separate editing of image thumbnails is deprecated and disabled since WordPress 6.3. This plugin re-enables it in order to maintain specific user requirements and workflows.\u003C\u002Fp>\n\u003Cp>WordPress has been using responsive images since version 4.4. Because of that having custom, non-proportional image sub-sizes is not considered a good practice. It reduces the number of images that can be used for responsive loading, and at the same time produces an image that cannot be loaded responsively as there are no other matching sizes for it.\u003C\u002Fp>\n\u003Cp>To re-enable editing and saving of image thumbnails separately, install and activate this plugin. To disable it again, deactivate and delete the plugin.\u003C\u002Fp>\n","Re-enables editing of the thumbnail size of images separately.",300,1947,100,6,"2023-08-03T22:58:00.000Z","6.3.8","6.3","7.0.0",[],"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fedit-image-thumbnails-separately\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fedit-image-thumbnails-separately.1.0.0.zip",85,0,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},"wordpressdotorg",34,14856200,97,1718,77,"2026-04-03T18:49:29.150Z",[],{"attackSurface":37,"codeSignals":49,"taintFlows":56,"riskAssessment":57,"analyzedAt":65},{"hooks":38,"ajaxHandlers":45,"restRoutes":46,"shortcodes":47,"cronEvents":48,"entryPointCount":23,"unprotectedCount":23},[39],{"type":40,"name":41,"callback":42,"file":43,"line":44},"filter","image_edit_thumbnails_separately","__return_true","edit-image-thumbnails-separately.php",24,[],[],[],[],{"dangerousFunctions":50,"sqlUsage":51,"outputEscaping":53,"fileOperations":23,"externalRequests":23,"nonceChecks":23,"capabilityChecks":23,"bundledLibraries":55},[],{"prepared":23,"raw":23,"locations":52},[],{"escaped":23,"rawEcho":23,"locations":54},[],[],[],{"summary":58,"deductions":59},"The 'edit-image-thumbnails-separately' plugin version 1.0.0 exhibits a strong security posture based on the provided static analysis. The complete absence of dangerous functions, external HTTP requests, file operations, and SQL queries that do not use prepared statements are all positive indicators. Furthermore, the code demonstrates excellent output escaping practices and a notable lack of critical or high severity taint flows, suggesting that the plugin does not expose users to common injection vulnerabilities.  The plugin's vulnerability history is also clean, with no recorded CVEs, further bolstering its security reputation.\n\nHowever, the analysis also highlights a significant concern: the complete absence of nonce and capability checks across all identified entry points, which are reported as zero. While the current attack surface appears minimal, this lack of fundamental WordPress security checks creates a potential weakness. If any entry points were to be introduced or discovered in the future, they would be inherently unprotected, making the plugin vulnerable to unauthorized actions.  The plugin's current strength lies in its apparent simplicity and lack of complex functionality, but this also means it has not been rigorously tested for more advanced security scenarios that would necessitate these checks. Therefore, while the current state is promising, the lack of security controls is a notable risk for future extensibility or broader adoption.",[60,63],{"reason":61,"points":62},"No nonce checks on any entry points",10,{"reason":64,"points":62},"No capability checks on any entry points","2026-03-16T19:53:34.182Z",{"wat":67,"direct":72},{"assetPaths":68,"generatorPatterns":69,"scriptPaths":70,"versionParams":71},[],[],[],[],{"cssClasses":73,"htmlComments":74,"htmlAttributes":75,"restEndpoints":76,"jsGlobals":77,"shortcodeOutput":78},[],[],[],[],[],[]]