[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f3hG9MFVbPkJGCfNyhFeHMdHRMbg-4gJc6hZIY5YtirM":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":24,"download_link":25,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28,"vulnerabilities":29,"developer":30,"crawl_stats":27,"alternatives":36,"analysis":133,"fingerprints":168},"autofields","Autofields","1.01.1","binnyva","https:\u002F\u002Fprofiles.wordpress.org\u002Fbinnyva\u002F","\u003Cp>This plugin will set the first paragraph of the content as the excerpt and take the first image(if there are any) and set it as the ‘Image’ custom field(needed for some themes). When you hit the publish button, it will check to make sure that excerpt and Image custom field are filled. If not, it will ask you to confirm before publishing the post.\u003C\u002Fp>\n\u003Ch3>How to Use\u003C\u002Fh3>\n\u003Cp>Activate the plugin and update the Settings(Settings > Autofields) of the plugin to your liking. Then just write posts – Autofields will auto fill some fields for you.\u003C\u002Fp>\n","AutoFields will auto fill the Excerpt and add an Image custom field based on the data you entered into the contents editor.",10,4466,0,"2014-03-13T15:00:00.000Z","3.7.41","2.5","",[19,20,21,22,23],"admin","autofill","excerpt","fields","post","http:\u002F\u002Fwww.bin-co.com\u002Ftools\u002Fwordpress\u002Fplugins\u002Fautofields\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fautofields.zip",85,null,"2026-03-15T15:16:48.613Z",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":31,"total_installs":32,"avg_security_score":26,"avg_patch_time_days":33,"trust_score":34,"computed_at":35},4,130,30,84,"2026-04-05T01:00:17.021Z",[37,55,76,96,116],{"slug":38,"name":39,"version":40,"author":41,"author_profile":42,"description":43,"short_description":44,"active_installs":45,"downloaded":46,"rating":13,"num_ratings":13,"last_updated":47,"tested_up_to":48,"requires_at_least":49,"requires_php":17,"tags":50,"homepage":53,"download_link":54,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"postlinks","PostLinks","0.2","Khanh","https:\u002F\u002Fprofiles.wordpress.org\u002Fkacao\u002F","\u003Cp>(Beta) An extension of Fields, a custom field management plugin. PostLinks provides additional field types such as Series, PhotoLink and PostLink.\u003C\u002Fp>\n\u003Cp>Three new field types:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>PostSeries: link your posts into series and display them with the [series] shortcode, also it comes with 2 widgets\u003C\u002Fli>\n\u003Cli>PhotoLink: to be added\u003C\u002Fli>\n\u003Cli>PostLink: to be added\u003C\u002Fli>\n\u003C\u002Ful>\n","(Beta) An extension of Fields, a custom field management plugin. PostLinks provides additional field types such as Series, PhotoLink and PostLink.",500,2597,"2010-08-18T00:49:00.000Z","3.0.5","3.0",[19,51,22,52,23],"custom","links","http:\u002F\u002Fcalce.net\u002Fpostlinks","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fpostlinks.zip",{"slug":56,"name":57,"version":58,"author":59,"author_profile":60,"description":61,"short_description":62,"active_installs":63,"downloaded":64,"rating":65,"num_ratings":66,"last_updated":67,"tested_up_to":68,"requires_at_least":68,"requires_php":17,"tags":69,"homepage":74,"download_link":75,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"more-taxonomies","More Taxonomies","1.1","henrikmelin","https:\u002F\u002Fprofiles.wordpress.org\u002Fhenrikmelin\u002F","\u003Cp>This is an early beta – fixes and better documentation to come. Promise.\u003C\u002Fp>\n","Add more taxonomies to your WordPress installation.",300,19281,100,1,"2011-09-02T15:42:00.000Z","3.2.1",[19,70,71,72,73],"cms","more-fields","post-types","taxonomies","http:\u002F\u002Flabs.dagensskiva.com\u002Fplugins\u002Fmore-taxonomies\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fmore-taxonomies.1.1.zip",{"slug":77,"name":78,"version":79,"author":80,"author_profile":81,"description":82,"short_description":83,"active_installs":63,"downloaded":84,"rating":85,"num_ratings":86,"last_updated":87,"tested_up_to":88,"requires_at_least":89,"requires_php":17,"tags":90,"homepage":94,"download_link":95,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"show-hidden-post-meta","Show Hidden Post Meta","1.0.1","Philip Newcomer","https:\u002F\u002Fprofiles.wordpress.org\u002Fphilipnewcomer\u002F","\u003Cp>This plugin makes all custom fields (post meta) visible in the “Custom Fields” meta box on post edit screens.\u003C\u002Fp>\n","Makes hidden post meta visible on post edit screens",8139,86,6,"2019-09-25T22:40:00.000Z","5.2.24","3.2",[19,91,92,93],"custom-fields","meta","post-meta","http:\u002F\u002Fwordpress.org\u002Fplugins\u002Fshow-hidden-post-meta\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fshow-hidden-post-meta.1.0.1.zip",{"slug":97,"name":98,"version":99,"author":100,"author_profile":101,"description":102,"short_description":103,"active_installs":63,"downloaded":104,"rating":85,"num_ratings":11,"last_updated":105,"tested_up_to":106,"requires_at_least":107,"requires_php":108,"tags":109,"homepage":113,"download_link":114,"security_score":115,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"wp-admin-search-meta","WP-Admin Search Post Meta","0.3","meloniq","https:\u002F\u002Fprofiles.wordpress.org\u002Fmeloniq\u002F","\u003Cp>Enables searching post meta fields on admin pages.\u003C\u002Fp>\n","Enables searching post meta fields on admin pages.",6412,"2024-11-21T22:59:00.000Z","6.7.5","4.9","5.6",[91,93,110,111,112],"postmeta","search","wp-admin","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-admin-search-meta\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-admin-search-meta.0.3.zip",92,{"slug":117,"name":118,"version":119,"author":120,"author_profile":121,"description":122,"short_description":123,"active_installs":124,"downloaded":125,"rating":65,"num_ratings":31,"last_updated":126,"tested_up_to":127,"requires_at_least":128,"requires_php":17,"tags":129,"homepage":131,"download_link":132,"security_score":65,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"list-more-custom-field-names","List More Custom Field Names","1.4.1","Scott Reilly","https:\u002F\u002Fprofiles.wordpress.org\u002Fcoffee2code\u002F","\u003Cp>By default, WordPress only allows 30 custom field names\u002Fkeys to be listed in the dropdown selection ‘Name’ field when writing a post or page. If you, or the plugins you use, make use of a lot of custom field key names, you may surpass the default limit resulting in some custom field keys not being listed. This may force post authors to manually type in custom field key names if they aren’t listed, which increases the chances for naming errors (typos, or not using the precise key name that is needed). This may also cause some authors concern wondering where previously used custom field keys have gone since they aren’t listed.\u003C\u002Fp>\n\u003Cp>This plugin increases the limit to 200 custom field key names.\u003C\u002Fp>\n\u003Cp>There is no settings page to customize the default value. If you’d like to list some number of custom field key names other than 200 (say, for example, 100), you can do so in either of two ways:\u003C\u002Fp>\n\u003Col>\n\u003Cli>By editing your wp-config.php file and at the end adding a line such as:\u003Cbr \u002F>\ndefine( ‘CUSTOM_FIELD_NAMES_LIMIT’, 100 );\u003Cbr \u002F>\n\u003Cem>-or-\u003C\u002Fem>\u003C\u002Fli>\n\u003Cli>Somewhere — ideally in a mu-plugin or site-specific plugin, or less ideally your active theme’s functions.php file — hook the ‘c2c_list_more_custom_field_names’ filter and return the number you’d like to use:\u003Cbr \u002F>\nadd_filter( ‘c2c_list_more_custom_field_names’, function ( $limist ) { return 100; } );\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>\u003Cem>Note:\u003C\u002Fem> This plugin has no effect for users who make use of the block editor (aka Gutenberg) introduced in WordPress v5.0 because that editor does not directly expose custom fields in the interface.\u003C\u002Fp>\n\u003Cp>Links: \u003Ca href=\"https:\u002F\u002Fcoffee2code.com\u002Fwp-plugins\u002Flist-more-custom-field-names\u002F\" rel=\"nofollow ugc\">Plugin Homepage\u003C\u002Fa> | \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Flist-more-custom-field-names\u002F\" rel=\"ugc\">Plugin Directory Page\u003C\u002Fa> | \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fcoffee2code\u002Flist-more-custom-field-names\u002F\" rel=\"nofollow ugc\">GitHub\u003C\u002Fa> | \u003Ca href=\"https:\u002F\u002Fcoffee2code.com\" rel=\"nofollow ugc\">Author Homepage\u003C\u002Fa>\u003C\u002Fp>\n","Allows for more existing custom field names to be listed in the dropdown selection field when writing a post.",80,9386,"2025-04-17T20:27:00.000Z","6.8.5","2.6",[19,91,130,92,23],"edit","https:\u002F\u002Fcoffee2code.com\u002Fwp-plugins\u002Flist-more-custom-field-names\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Flist-more-custom-field-names.1.4.1.zip",{"attackSurface":134,"codeSignals":154,"taintFlows":161,"riskAssessment":162,"analyzedAt":167},{"hooks":135,"ajaxHandlers":150,"restRoutes":151,"shortcodes":152,"cronEvents":153,"entryPointCount":13,"unprotectedCount":13},[136,142,146],{"type":137,"name":138,"callback":139,"file":140,"line":141},"action","admin_menu","autofields_option_page","autofields.php",14,{"type":137,"name":143,"callback":144,"file":140,"line":145},"edit_form_advanced","autofields_insert_script",29,{"type":137,"name":147,"callback":148,"file":140,"line":149},"activate_autofields\u002Fautofields.php","autofields_activate",127,[],[],[],[],{"dangerousFunctions":155,"sqlUsage":156,"outputEscaping":158,"fileOperations":13,"externalRequests":13,"nonceChecks":13,"capabilityChecks":66,"bundledLibraries":160},[],{"prepared":13,"raw":13,"locations":157},[],{"escaped":13,"rawEcho":13,"locations":159},[],[],[],{"summary":163,"deductions":164},"The autofields plugin v1.01.1 exhibits a strong security posture based on the provided static analysis. The complete absence of entry points like AJAX handlers, REST API routes, and shortcodes significantly limits the potential attack surface.  Furthermore, the code demonstrates excellent security practices with 100% of SQL queries using prepared statements and 100% of output being properly escaped. The presence of capability checks also indicates an effort to enforce access control.\n\nHowever, the static analysis reveals a notable concern: zero nonce checks. While the absence of directly exploitable entry points mitigates immediate risk, the lack of nonce checks is a critical omission that could lead to Cross-Site Request Forgery (CSRF) vulnerabilities if any interaction points were to be introduced in future versions or if hidden interactions exist. The taint analysis showing zero flows with unsanitized paths is positive, but the absence of nonce checks is a fundamental security control that should be present.\n\nThe plugin's vulnerability history is clean, with no recorded CVEs, which is a very positive sign. This suggests that the plugin has been developed with security in mind or has been well-maintained to avoid known vulnerabilities.  In conclusion, autofields v1.01.1 is remarkably secure in its current state due to its minimal attack surface and adherence to secure coding practices for SQL and output. The primary weakness is the complete lack of nonce checks, which represents a potential future risk.",[165],{"reason":166,"points":11},"No nonce checks implemented","2026-03-17T01:08:31.011Z",{"wat":169,"direct":175},{"assetPaths":170,"generatorPatterns":171,"scriptPaths":172,"versionParams":174},[],[],[173],"\u002Fwp-content\u002Fplugins\u002Fautofields\u002Fautofields.php",[],{"cssClasses":176,"htmlComments":177,"htmlAttributes":178,"restEndpoints":179,"jsGlobals":180,"shortcodeOutput":184},[],[],[],[],[181,182,183],"autofields_init","autofields_getContents","autofields_check",[]]