[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f9QL56E1lj4T3TmDlZE5YUJs2yDGMEDs9GyUbXjc8rTw":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":138,"fingerprints":163},"acf-unique-id-field","Advanced Custom Fields: Unique ID Field","1.0.0","KLicheR","https:\u002F\u002Fprofiles.wordpress.org\u002Fklicher\u002F","\u003Cp>Create a unique ID to easily identify repeater field’s rows. The field is fulfill on the first “save” of the post.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Compatibility\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>This ACF field type is compatible with:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>ACF 5\u003C\u002Fli>\n\u003C\u002Ful>\n","Create a unique ID to easily identify repeater field's rows.",3000,19946,100,6,"2014-12-05T19:14:00.000Z","4.0.38","3.5","",[20,21,22],"acf","id","unique","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Facf-unique-id-field","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Facf-unique-id-field.1.0.0.zip",85,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":25,"avg_patch_time_days":34,"trust_score":35,"computed_at":36},"klicher",2,3040,30,84,"2026-04-04T15:38:14.055Z",[38,60,77,96,118],{"slug":39,"name":40,"version":41,"author":42,"author_profile":43,"description":44,"short_description":45,"active_installs":11,"downloaded":46,"rating":47,"num_ratings":48,"last_updated":49,"tested_up_to":50,"requires_at_least":51,"requires_php":18,"tags":52,"homepage":57,"download_link":58,"security_score":59,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"acf-vc-integrator","ACF-VC Integrator","1.8.7","Kåre Mulvad Steffensen","https:\u002F\u002Fprofiles.wordpress.org\u002Fdejliglama\u002F","\u003Cp>Advanced Custom Fields right inside your WPBakery Page Builder\u003C\u002Fp>\n\u003Cp>The ACF-VC Plugin puts a ACF element into your WPBakery Page Builder, making it easier than ever to use your custom created fields in your own page design.\u003C\u002Fp>\n\u003Cp>All Advanced Custom Fields are supported, and easy to target with your own CSS classes for ultimative design possibilities.\u003C\u002Fp>\n","ACF-VC Plugin puts a ACF element into your WPBakery Page Builder making it easier than ever to use your custom created fields in your own page design.",73540,98,19,"2025-02-03T17:20:00.000Z","6.6.5","4.4.0",[20,53,54,55,56],"advanced-custom-fields","grid-builder","templatera","wpbakery-page-builder","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Facf-vc-integrator\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Facf-vc-integrator.1.8.7.zip",92,{"slug":61,"name":62,"version":63,"author":64,"author_profile":65,"description":66,"short_description":67,"active_installs":11,"downloaded":68,"rating":13,"num_ratings":69,"last_updated":70,"tested_up_to":71,"requires_at_least":72,"requires_php":18,"tags":73,"homepage":75,"download_link":76,"security_score":13,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"post-2-post-for-acf","ACF Post-2-Post","1.7.0","John Huebner","https:\u002F\u002Fprofiles.wordpress.org\u002Fhube2\u002F","\u003Cp>\u003Cstrong>\u003Cem>This is an add on plugin for Advanced Custom Fields (ACF) >= Version 5.\u003C\u002Fem>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>\u003Cem>This plugin will not work with ACF Version 4.\u003C\u002Fem>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>This plugin will not provide any functionality if ACF >=5 is not installed.***\u003C\u002Fp>\n\u003Cp>This plugin does not create a new type of field or any admin interface. This plugin when used as\u003Cbr \u002F>\nexplained below makes the existing ACF Relationship and Post Object fields work bi-directionaly,\u003Cbr \u002F>\nautomatically updating the relationship field on the other end of the relationship.\u003C\u002Fp>\n\u003Cp>For more information see \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fpost-2-post-for-acf\u002F\" rel=\"ugc\">Other Notes\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch3>Github Repository\u003C\u002Fh3>\n\u003Cp>This plugin is also on GitHub\u003Cbr \u002F>\n\u003Ca href=\"https:\u002F\u002Fgithub.com\u002FHube2\u002Facf-post2post\" rel=\"nofollow ugc\">https:\u002F\u002Fgithub.com\u002FHube2\u002Facf-post2post\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch3>How To Use\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Create a relationship or post object field.\u003C\u002Fli>\n\u003Cli>The field must be at the top level. It cannot be a subfield of a repeater or a flexible content field.\u003C\u002Fli>\n\u003Cli>The field name must be the same on all posts. In other words if you want to have different post types be related then you must add a field with the same field name on both post types.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>When you add a post to a relationship or post object field and the same field name appears on the post added to the relationship then the relationship field on the related post will be updated to include a relationship to the post being edited.\u003C\u002Fp>\n\u003Cp>If a post is removed from a relationship then the post being removed will also be updated to remove the relationship to the post being edited.\u003C\u002Fp>\n\u003Ch3>Post Object Fields\u003C\u002Fh3>\n\u003Cp>If a post object field is being used\u003C\u002Fp>\n\u003Cul>\n\u003Cli>If it allows multiple values then it will work the same way that relationship fields work.\u003C\u002Fli>\n\u003Cli>If it does not allow multiple values and the related post already contains a value see Overwrite Settings\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Overwrite Settings\u003C\u002Fh3>\n\u003Cp>If the field in a related post, whether it is a post object field that only allows 1 value or a relationship field that has a maximum number of related posts, if the field in the related post already has the maximum number of values allowed, by default, a new value will not be added. You can override this default by specifying overwrite settings.\u003C\u002Fp>\n\u003Cp>How to add overwrite settings\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_filter('acf-post2post\u002Foverwrite-settings', 'my_overwrite_settings');\nfunction my_overwrite_settings($settings) {\n  $settings['field_name'] = array(\n      'overwrite' => true,\n        'type' => 'first'\n  );\n  return $settings;\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Each element of the $settings array is an array. The index of the array is the field that you want to specify settings for. Each field can have 2 arguments.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>overwrite: true\u002Ffalse or 1\u002F0. If set to true or 1 then new values will overwrite older values. The default value of this setting is false.\u003C\u002Fli>\n\u003Cli>type: ‘first’ or ‘last’. Which of the existing values should be removed, the first one added or the last. The default value is ‘first’.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>after a value is removed from the existing list the new value is added to the end of the list.\u003C\u002Fp>\n\u003Ch3>Field Exeptions\u003C\u002Fh3>\n\u003Cp>You can disable automatic bidirectional relationships for specific field keys using the filter\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F\u002F field_XXXXXXXX = the field key of the field\n\u002F\u002F you want to disable bidirectional relationships for\nadd_filter('acf\u002Fpost2post\u002Fupdate_relationships\u002Fkey=field_XXXXXXXX', '__return_false');\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3>After update hooks\u003C\u002Fh3>\n\u003Cp>There are two actions that can be used after a post is updated and passes a single post ID. Please make sure you see the subtle difference in these two hooks.\u003C\u002Fp>\n\u003Cp>The first is run after each related post is updated\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_action('acf\u002Fpost2post\u002Frelationship_updated', 'my_post_updated_action');\nfunction my_post_updated_action($post_id) {\n  \u002F\u002F $post_id == the post ID that was updated\n  \u002F\u002F do something after the related post is updated\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>The second is run after all posts are updated and passes an array of post IDs.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_action('acf\u002Fpost2post\u002Frelationships_updated', 'my_post_updated_action');\nfunction my_post_updated_action($posts) {\n  \u002F\u002F $posts == and array of post IDs that were updated\n    \u002F\u002F do something to all posts after update\n    foreach ($posts as $post_id) {\n      \u002F\u002F do something to post\n    }\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n","Automatic Two Way (Bidirectional) Relationships with ACF",68004,39,"2025-07-09T13:44:00.000Z","6.9.4","4.0",[20,74],"bidirectional-relationship","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fpost-2-post-for-acf\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fpost-2-post-for-acf.1.7.0.zip",{"slug":78,"name":79,"version":80,"author":81,"author_profile":82,"description":83,"short_description":84,"active_installs":85,"downloaded":86,"rating":35,"num_ratings":87,"last_updated":88,"tested_up_to":50,"requires_at_least":89,"requires_php":90,"tags":91,"homepage":94,"download_link":95,"security_score":59,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"acf-hide-layout","ACF Hide Layout","1.2.1","Bleech","https:\u002F\u002Fprofiles.wordpress.org\u002Fbleechberlin\u002F","\u003Cp>Sometimes you may need to hide\u002Fremove a flexible content layout from showing on the frontend of the website, but you would still like to keep it in the backend in case you need to re-enable that layout again in the future.\u003C\u002Fp>\n\u003Cp>Of course you can always just remove the layout, but if it’s a complex group of fields with a lot of data, re-creating it later would be a pain. And here the \u003Cstrong>ACF Hide Layout\u003C\u002Fstrong> plugin comes into play. It adds a small button with an “eye” icon to easily disable\u002Fenable flexible layout content without removing it.\u003C\u002Fp>\n\u003Cp>See more info on the \u003Ca href=\"https:\u002F\u002Fflyntwp.com\u002Facf-hide-layout\u002F\" rel=\"nofollow ugc\">plugin website\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch3>Requirements\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002F\" rel=\"ugc\">WordPress\u003C\u002Fa> >= 4.7\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwww.advancedcustomfields.com\u002Fpro\u002F\" rel=\"nofollow ugc\">Advanced Custom Fields Pro\u003C\u002Fa> >= 5.7\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Development\u003C\u002Fh3>\n\u003Cp>The source code can be found on \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fflyntwp\u002Facf-hide-layout\" rel=\"nofollow ugc\">GitHub\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Made by people who brought to you \u003Ca href=\"https:\u002F\u002Fflyntwp.com\u002F?utm_source=WordPress%20Plugin%20Directory&utm_medium=Link&utm_campaign=ACF%20Hide%20Layout%20Plugin\" rel=\"nofollow ugc\">Flynt – The Component Based WordPress Starter Theme\u003C\u002Fa>\u003C\u002Fp>\n","Easily hide the layout of the flexible content on the frontend but still keep it in the backend.",2000,15049,5,"2024-07-19T12:39:00.000Z","4.7","5.6",[20,53,92,93],"flexible-content","hide-layout","https:\u002F\u002Fflyntwp.com\u002Facf-hide-layout\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Facf-hide-layout.1.2.1.zip",{"slug":97,"name":98,"version":99,"author":100,"author_profile":101,"description":102,"short_description":103,"active_installs":85,"downloaded":104,"rating":105,"num_ratings":87,"last_updated":106,"tested_up_to":107,"requires_at_least":108,"requires_php":109,"tags":110,"homepage":116,"download_link":117,"security_score":13,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"acf-nav-menu-field","ACF Nav Menu Field","1.7","Galaxy Weblinks","https:\u002F\u002Fprofiles.wordpress.org\u002Fgalaxyweblinks\u002F","\u003Cp>ACF Nav Menu field provides navigation menu field type in the field groups and displays on posts, pages, users, taxonomy terms, media, comments, and even custom options pages. We can call and display the menu as ACF using the get_field() function.\u003C\u002Fp>\n\u003Cp>Here’s a link to the documentation for the plugin. This will help you learn more about its features and how to use it.\u003Cbr \u002F>\n\u003Cstrong>\u003C\u002Fstrong>\u003Cstrong>\u003Ca href=\"https:\u002F\u002Fwp-plugins.galaxyweblinks.com\u002Fwp-plugins\u002Facf-nav-menu-field\u002Fdoc\u002F\" rel=\"nofollow ugc\">Documentation\u003C\u002Fa>\u003C\u002Fstrong>\u003Cbr \u002F>\nFor any feedback or queries regarding this plugin, please contact our \u003Ca href=\"https:\u002F\u002Fwp-plugins.galaxyweblinks.com\u002Fcontact\u002F\" rel=\"nofollow ugc\">Support team\u003C\u002Fa>.\u003C\u002Fp>\n","ACF Nav Menu field plugin provides an option to show a menu in the front end similar to other ACF fields (Text, Textarea, Number, Range etc.)",17697,52,"2025-04-24T05:22:00.000Z","6.8.5","5.8.8","7.4",[111,112,113,114,115],"acf-field","menu","nav","select","sidebar","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Facf-nav-menu\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Facf-nav-menu-field.1.7.zip",{"slug":119,"name":120,"version":121,"author":122,"author_profile":123,"description":124,"short_description":125,"active_installs":85,"downloaded":126,"rating":127,"num_ratings":128,"last_updated":129,"tested_up_to":130,"requires_at_least":131,"requires_php":132,"tags":133,"homepage":18,"download_link":137,"security_score":25,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"cf7-submission-id","UniqueID for Contact Form 7","2.4.0","tsjippy","https:\u002F\u002Fprofiles.wordpress.org\u002Ftsjippy\u002F","\u003Cp>Plugin for Contact Form 7: adds a field for an unique submission id.\u003Cbr \u002F>\nYou can choose to include a hidden or an visible field to your form.\u003Cbr \u002F>\nThis field will be automatically filled with an number which is incremented on every submission.\u003C\u002Fp>\n\u003Ch3>Usage\u003C\u002Fh3>\n\u003Cp>Just add the field to your form.\u003C\u002Fp>\n\u003Cp>You can filter the value using the cf7_submission_id_filter.\u003Cbr \u002F>\nTo add leading zeros for example, just put the code below in your functions.php\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_filter('cf7_submission_id_filter', 'custom_cf7_submission_id_filter');\nfunction custom_cf7_submission_id_filter($val){\n    return sprintf(\"%04d\", $val);\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n","An add-on for Contact Form 7 to add an unique id to every form submission.",20459,54,10,"2021-04-01T13:22:00.000Z","5.7.0","4.0.0","5.2.4",[134,135,136],"contact-form-7","submission-id","unique-id","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcf7-submission-id.zip",{"attackSurface":139,"codeSignals":150,"taintFlows":158,"riskAssessment":159,"analyzedAt":162},{"hooks":140,"ajaxHandlers":146,"restRoutes":147,"shortcodes":148,"cronEvents":149,"entryPointCount":26,"unprotectedCount":26},[141],{"type":142,"name":143,"callback":144,"file":145,"line":34},"action","acf\u002Finclude_field_types","include_field_types_unique_id","acf-unique_id.php",[],[],[],[],{"dangerousFunctions":151,"sqlUsage":152,"outputEscaping":154,"fileOperations":26,"externalRequests":26,"nonceChecks":26,"capabilityChecks":26,"bundledLibraries":157},[],{"prepared":26,"raw":26,"locations":153},[],{"escaped":155,"rawEcho":26,"locations":156},4,[],[],[],{"summary":160,"deductions":161},"The ACF Unique ID Field plugin v1.0.0 demonstrates an exceptionally strong security posture based on the provided static analysis and vulnerability history. The absence of any identified attack surface entry points like AJAX handlers, REST API routes, shortcodes, or cron events significantly limits potential exploitation vectors. Furthermore, the code signals indicate robust security practices, with no dangerous functions, all SQL queries using prepared statements, and all output properly escaped. The lack of file operations, external HTTP requests, nonce checks, and capability checks (while potentially indicative of a very simple plugin) means there are no evident code-level vulnerabilities related to these common attack vectors.\n\nThe vulnerability history is also pristine, with zero known CVEs, indicating a history of stable and secure development. This, combined with the static analysis results, suggests that the plugin is well-written and has likely undergone thorough security review or has simply not been a target due to its limited functionality. The plugin's strengths lie in its apparent simplicity and adherence to secure coding principles where applicable.\n\nHowever, the total absence of nonces and capability checks across all entry points (though there are zero entry points) does present a theoretical concern if the plugin were to evolve and introduce features that handle user input or sensitive actions. For its current state (v1.0.0), the risk is negligible, but future development should carefully consider implementing these checks. In conclusion, this version of the plugin appears to be highly secure with no exploitable weaknesses detected in the provided data.",[],"2026-03-16T18:22:58.158Z",{"wat":164,"direct":173},{"assetPaths":165,"generatorPatterns":168,"scriptPaths":169,"versionParams":170},[166,167],"\u002Fwp-content\u002Fplugins\u002Facf-unique-id-field\u002Fassets\u002Fcss\u002Facf-unique-id-field.css","\u002Fwp-content\u002Fplugins\u002Facf-unique-id-field\u002Fassets\u002Fjs\u002Facf-unique-id-field.js",[],[167],[171,172],"acf-unique-id-field\u002Fassets\u002Fcss\u002Facf-unique-id-field.css?ver=","acf-unique-id-field\u002Fassets\u002Fjs\u002Facf-unique-id-field.js?ver=",{"cssClasses":174,"htmlComments":176,"htmlAttributes":177,"restEndpoints":179,"jsGlobals":180,"shortcodeOutput":182},[175],"acf-unique-id-field-wrap",[],[178],"data-unique-id-field-options",[],[181],"acf_unique_id_field_options",[]]