[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fRB8A2EG3g2XxWmwUhkxKytsQabNcZloVLoMMgIB7w-0":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":8,"download_link":24,"security_score":25,"vuln_count":13,"unpatched_count":13,"last_vuln_date":26,"fetched_at":27,"vulnerabilities":28,"developer":29,"crawl_stats":26,"alternatives":37,"analysis":138,"fingerprints":207},"metaviewer-debug-meta-data","MetaViewer – Debug Meta Data","1.0.0","Usman Ali Qureshi","https:\u002F\u002Fprofiles.wordpress.org\u002Fusmanaliqureshi\u002F","\u003Cp>\u003Cstrong>MetaViewer\u003C\u002Fstrong> helps developers and advanced users view all post meta and user meta data in a clear, organized table format. It supports custom post types and displays the data type of each value (string, integer, array, etc.).\u003C\u002Fp>\n\u003Cp>This plugin is useful for debugging, development, or reviewing what’s stored in WordPress meta fields.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Key Features:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>View post meta data on the edit screen of all post types.\u003C\u002Fli>\n\u003Cli>View user meta data on user profile pages.\u003C\u002Fli>\n\u003Cli>Clean tabular layout with zebra striping.\u003C\u002Fli>\n\u003Cli>Auto-detects and displays data types (string, int, array, etc.).\u003C\u002Fli>\n\u003Cli>Translation ready and lightweight.\u003C\u002Fli>\n\u003Cli>Compatible with PHP 7.4 to 8.3.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>License\u003C\u002Fh3>\n\u003Cp>This plugin is licensed under the GPLv2 or later.\u003C\u002Fp>\n","View and debug post and user meta data in a clean table format – lightweight, dev-friendly, and works across post types in the WP admin.",10,364,0,"2025-05-26T08:31:00.000Z","6.8.5","5.5","7.4",[19,20,21,22,23],"debug-meta","inspect-meta","meta-data","post-meta","user-meta","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fmetaviewer-debug-meta-data.1.0.0.zip",100,null,"2026-03-15T15:16:48.613Z",[],{"slug":30,"display_name":7,"profile_url":8,"plugin_count":31,"total_installs":32,"avg_security_score":33,"avg_patch_time_days":34,"trust_score":35,"computed_at":36},"usmanaliqureshi",4,5010,98,30,93,"2026-04-04T10:37:27.792Z",[38,59,81,100,120],{"slug":39,"name":40,"version":41,"author":42,"author_profile":43,"description":44,"short_description":45,"active_installs":46,"downloaded":47,"rating":25,"num_ratings":48,"last_updated":49,"tested_up_to":50,"requires_at_least":51,"requires_php":52,"tags":53,"homepage":57,"download_link":58,"security_score":25,"vuln_count":13,"unpatched_count":13,"last_vuln_date":26,"fetched_at":27},"view-user-metadata","View User Metadata","1.2.2","Sully","https:\u002F\u002Fprofiles.wordpress.org\u002Fss88_uk\u002F","\u003Cp>Introducing our new lightweight WordPress plugin – View User Metadata!\u003C\u002Fp>\n\u003Cp>\u003Cspan class=\"embed-youtube\" style=\"text-align:center; display: block;\">\u003Ciframe loading=\"lazy\" class=\"youtube-player\" width=\"750\" height=\"422\" src=\"https:\u002F\u002Fwww.youtube.com\u002Fembed\u002FLgWdTlLw8BQ?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent\" allowfullscreen=\"true\" style=\"border:0;\" sandbox=\"allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox\">\u003C\u002Fiframe>\u003C\u002Fspan>\u003C\u002Fp>\n\u003Cp>This plugin adds a simple toggle button to the user edit screen, allowing administrators to easily view metadata associated with the user they are currently viewing. Metadata includes all data attached to a user account. Administrator’s can also delete the usermeta.\u003C\u002Fp>\n\u003Cp>This plugin is perfect for developers where metadata is important to view but doesn’t need to be displayed at all times.\u003C\u002Fp>\n\u003Cp>Features:\u003Cbr \u002F>\n– Toggle to show\u002Fhide user data\u003Cbr \u002F>\n– Click-to-focus on any row\u003Cbr \u002F>\n– Delete a key\u002Fvalue pair\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Check out our other plugins:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>🎉 \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fmedia-library-file-size\u002F\" rel=\"ugc\">Media Library File Size\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>✨ \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fsingle-post-page-export\u002F\" rel=\"ugc\">Export Single Post Page\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>🔒 \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Ftwo-factor-2fa-via-email\u002F\" rel=\"ugc\">Two Factor (2FA) Authentication via Email\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>🔠 \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fenable-turnstile-cloudflare-for-gravity-forms\u002F\" rel=\"ugc\">Enable Turnstile (Cloudflare) for Gravity Forms\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>⭐️⭐️⭐️⭐️⭐️ \u003Ca href=\"https:\u002F\u002Fss88.us\u002Fplugins\u002Fgravity-forms-freescout?utm_campaign=OtherPlugins\" rel=\"nofollow ugc\">Gravity Forms to FreeScout\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n","A lightweight plugin that allows you to view user metadata, export them CSV or JSON, or delete key\u002Fvalue pairs.",1000,12103,1,"2026-02-05T16:58:00.000Z","6.9.4","4.6","5.6",[54,23,55,56],"metdata","user-meta-data","user-metadata","https:\u002F\u002Fneoboffin.com\u002Fplugins\u002Fview-user-metadata","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fview-user-metadata.1.2.2.zip",{"slug":60,"name":61,"version":62,"author":63,"author_profile":64,"description":65,"short_description":66,"active_installs":67,"downloaded":68,"rating":69,"num_ratings":70,"last_updated":71,"tested_up_to":72,"requires_at_least":73,"requires_php":74,"tags":75,"homepage":78,"download_link":79,"security_score":80,"vuln_count":13,"unpatched_count":13,"last_vuln_date":26,"fetched_at":27},"custom-metadata","Custom Metadata Manager","0.7.1","Mohammad Jangda","https:\u002F\u002Fprofiles.wordpress.org\u002Fbatmoo\u002F","\u003Cp>An easy way to add custom fields to your object types (post, pages, custom post types, users) & to generate option pages.\u003C\u002Fp>\n\u003Cp>The goal of this plugin is to help you rapidly build familiar, intuitive interfaces for your users in a very WordPress-native way.\u003C\u002Fp>\n\u003Cp>The custom field panel is nice, but not quite the easiest thing for users to work with. Adding your own metaboxes and fields involves a lot of time and repetitive code that could be better used elsewhere.\u003C\u002Fp>\n\u003Cp>This plugin handles all that heavy-lifting for you behind-the-scenes, so that you can focus on more on building out and connecting your data rather than all the minor details. This single piece of code \u003Ccode>x_add_metadata_field( 'my-field-name', 'post' );\u003C\u002Fcode> generates a metabox with a text field inside it, with the necessary hooks to save the entered values.\u003C\u002Fp>\n\u003Cp>The API is similar to that used for registering custom post types and taxonomies so it should be familiar territory.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>NOTE\u003C\u002Fstrong>: The plugin now requires WordPress 3.3+ (chiefly for the wysiwyg & datepicker fields)\u003C\u002Fp>\n\u003Cp>Like what you see? Want more field types and features added? \u003Ca href=\"mailto:tech@stresslimitdesign.com\" rel=\"nofollow ugc\">Get in touch\u003C\u002Fa> or \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fjkudish\u002Fcustom-metadata\" rel=\"nofollow ugc\">contribute on github\u003C\u002Fa>\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>\u003Cem>See “Other Notes” section for usage information\u003C\u002Fem>\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch3>Usage\u003C\u002Fh3>\n\u003Ch4>Object Types\u003C\u002Fh4>\n\u003Cp>The main idea behind this plugin is to have a single API to work with regardless of the object type. Currently, Custom Metadata Manager works with \u003Ccode>user\u003C\u002Fcode>, \u003Ccode>comment\u003C\u002Fcode> and any built-in or custom post types, e.g. \u003Ccode>post\u003C\u002Fcode>, \u003Ccode>page\u003C\u002Fcode>, etc.\u003C\u002Fp>\n\u003Ch4>Registering your fields\u003C\u002Fh4>\n\u003Cp>For the sake of performance (and to avoid potential race conditions), always register your custom fields in the \u003Ccode>admin_menu\u003C\u002Fcode> hook. This way your front-end doesn’t get bogged down with unnecessary processing and you can be sure that your fields will be registered safely. Here’s a code sample:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_action( 'admin_menu', 'my_theme_init_custom_fields' );\n\nfunction my_theme_init_custom_fields() {\n    if( function_exists( 'x_add_metadata_field' ) && function_exists( 'x_add_metadata_group' ) ) {\n        x_add_metadata_field( 'my_field', array( 'user', 'post' ) );\n    }\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Getting the data\u003C\u002Fh4>\n\u003Cp>You can get the data as you normally would using the \u003Ccode>get_metadata\u003C\u002Fcode> function. Custom Metadata manager stores all data using the WordPress metadata APIs using the slug name you provide. That way, even if you decide to deactivate this wonderful plugin, your data is safe and accessible. For options, you can use \u003Ccode>get_option\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>Example:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$value = get_metadata( 'post', get_the_ID(), 'featured', true ); \u002F\u002F Returns post metadata value for the field 'featured'\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Adding Metadata Groups\u003C\u002Fh4>\n\u003Cp>A group is essentially a metabox that groups together multiple fields. Register the group before any fields\u003C\u002Fp>\n\u003Cpre>\u003Ccode>x_add_metadata_group( $slug, $object_types, $args );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Parameters\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>$slug\u003C\u002Fcode> (string) The key under which the metadata will be stored.\u003C\u002Fli>\n\u003Cli>\u003Ccode>$object_types\u003C\u002Fcode> (string|array) The object types to which this field should be added. Supported: post, page, any custom post type, user, comment.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Options and Overrides\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$args = array(\n    'label' => $group_slug, \u002F\u002F Label for the group\n    'context' => 'normal', \u002F\u002F (post only)\n    'priority' => 'default', \u002F\u002F (post only)\n    'autosave' => false, \u002F\u002F (post only) Should the group be saved in autosave? NOT IMPLEMENTED YET!\n    'exclude' => '', \u002F\u002F see below for details\n    'include' => '', \u002F\u002F see below for details\n);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Adding Metadata Fields\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>x_add_metadata_field( $slug, $object_types, $args );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Parameters\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>$slug\u003C\u002Fcode> (string) The key under which the metadata will be stored. For post_types, prefix the slug with an underscore (e.g. \u003Ccode>_hidden\u003C\u002Fcode>) to hide it from the the Custom Fields box.\u003C\u002Fli>\n\u003Cli>\u003Ccode>$object_types\u003C\u002Fcode> (string|array) The object types to which this field should be added. Supported: post, page, any custom post type, user, comment.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Options and Overrides\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$args = array(\n    'group' => '', \u002F\u002F The slug of group the field should be added to. This needs to be registered with x_add_metadata_group first.\n    'field_type' => 'text', \u002F\u002F The type of field; 'text', 'textarea', 'password', 'checkbox', 'radio', 'select', 'upload', 'wysiwyg', 'datepicker', 'taxonomy_select', 'taxonomy_radio'\n    'label' => '', \u002F\u002F Label for the field\n    'description' => '', \u002F\u002F Description of the field, displayed below the input\n    'values' => array(), \u002F\u002F Values for select and radio buttons. Associative array\n    'display_callback' => '', \u002F\u002F Callback to custom render the field\n    'sanitize_callback' => '', \u002F\u002F Callback to sanitize data before it's saved\n    'display_column' => false, \u002F\u002F Add the field to the columns when viewing all posts\n    'display_column_callback' => '', \u002F\u002F Callback to render output for the custom column\n    'required_cap' => '', \u002F\u002F The cap required to view and edit the field\n    'exclude' => '', \u002F\u002F see below for details\n    'include' => '', \u002F\u002F see below for details\n    'multiple' => false, \u002F\u002F true or false, can the field be duplicated with a click of a button?\n    'readonly' => false, \u002F\u002F makes the field be readonly (works with text, textarea, password, upload and datepicker fields)\n);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Include \u002F Exclude\u003C\u002Fh4>\n\u003Cp>You can exclude fields and groups from specific object. For example, with the following, field-1 will show up for all posts except post #123:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$args = array(\n    'exclude' => 123\n);\nx_add_metadata_field( 'field-1', 'post', $args );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Alternatively, you can limit (“include”) fields and groups to specific objects. The following will ”only” show group-1 to post #456:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$args = array(\n    'include' => 123\n);\nx_add_metadata_group( 'group-1', 'post', $args );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>You can pass in an array of IDs:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$args = array(\n    'include' => array( 123, 456, 789 );\n);\n\nWith multiple object types, you can pass in an associative array:\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>$args = array(\u003Cbr \u002F>\n    ‘exclude’ => array(\u003Cbr \u002F>\n        ‘post’ => 123,\u003Cbr \u002F>\n        ‘user’ => array( 123, 456, 789 )\u003Cbr \u002F>\n    )\u003Cbr \u002F>\n);\u003C\u002Fp>\n\u003Ch4>Examples\u003C\u002Fh4>\n\u003Cp>For examples, please see the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fjkudish\u002Fcustom-metadata\u002Fblob\u002Fmaster\u002Fcustom_metadata_examples.php\" rel=\"nofollow ugc\">custom_metadata_examples.php\u003C\u002Fa> file included with the plugin. Add a constant to your wp-config.php called \u003Ccode>CUSTOM_METADATA_MANAGER_DEBUG\u003C\u002Fcode> with a value of \u003Ccode>true\u003C\u002Fcode> to see it in action:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'CUSTOM_METADATA_MANAGER_DEBUG', true );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>TODOs\u003C\u002Fh4>\n\u003Cp>Stuff we have planned for the future:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Ability to clone (multiple) groups of fields\u003C\u002Fli>\n\u003Cli>Ability Pass in attributes for built-in fields (e.g. class, data-*, etc.)\u003C\u002Fli>\n\u003Cli>Additional field types (multi-select, multi-checkbox)\u003C\u002Fli>\n\u003Cli>Limit or exclude groups and fields using a custom callback\u003C\u002Fli>\n\u003Cli>Autosave support for fields on post types\u003C\u002Fli>\n\u003Cli>Client- and server-side validation support\u003C\u002Fli>\n\u003Cli>Add groups and fields to Quick Edit\u003C\u002Fli>\n\u003C\u002Ful>\n","An easy way to add custom fields to your object types (post, pages, custom post types, users)",800,16509,88,5,"2012-07-11T19:02:00.000Z","3.4.2","3.3","",[60,76,22,77,23],"custom-metadata-manager-metadata","postmeta","http:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fcustom-metadata\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcustom-metadata.0.7.1.zip",85,{"slug":82,"name":83,"version":84,"author":85,"author_profile":86,"description":87,"short_description":88,"active_installs":89,"downloaded":90,"rating":25,"num_ratings":91,"last_updated":92,"tested_up_to":50,"requires_at_least":93,"requires_php":17,"tags":94,"homepage":98,"download_link":99,"security_score":25,"vuln_count":13,"unpatched_count":13,"last_vuln_date":26,"fetched_at":27},"metadata-viewer","Metadata Viewer","2.1.1","PluginizeLab","https:\u002F\u002Fprofiles.wordpress.org\u002Fpluginizelab\u002F","\u003Cp>The Metadata Viewer plugin displays post, user (ie. posts, pages, and custom post types, user, WooCommerce products & orders) meta keys and their values at the bottom of the post & user editing page. There is also integrated realtime search feature.\u003Cbr \u002F>\nJust install a single plugin to solve multiple purpose like to show posts, pages, custom post types & user meta.\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Posts Metadata Viewer\u003C\u002Fli>\n\u003Cli>Custom Post Types Metadata Viewer\u003C\u002Fli>\n\u003Cli>Pages Metadata Viewer\u003C\u002Fli>\n\u003Cli>Users Metadata Viewer\u003C\u002Fli>\n\u003Cli>WooCommerce Products Metadata Viewer\u003C\u002Fli>\n\u003Cli>WooCommerce Orders Metadata Viewer\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Up-Comming Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Comment Metadata Viewer\u003C\u002Fli>\n\u003Cli>Term Metadata Viewer\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Support\u003C\u002Fh3>\n\u003Cp>If you find this plugin useful, consider supporting its development through a \u003Ca href=\"https:\u002F\u002Fwww.buymeacoffee.com\u002Faiarnob\" rel=\"nofollow ugc\">donation\u003C\u002Fa>.\u003C\u002Fp>\n","A plugin or theme developer can view metadata by this plugin easily.",300,2682,2,"2025-12-24T10:56:00.000Z","6.0.0",[95,96,97,22,23],"custom-post-type-meta","meta-viewer","metadata","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fmetadata-viewer","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fmetadata-viewer.2.1.1.zip",{"slug":101,"name":102,"version":103,"author":104,"author_profile":105,"description":106,"short_description":107,"active_installs":108,"downloaded":109,"rating":25,"num_ratings":110,"last_updated":111,"tested_up_to":112,"requires_at_least":113,"requires_php":74,"tags":114,"homepage":118,"download_link":119,"security_score":80,"vuln_count":13,"unpatched_count":13,"last_vuln_date":26,"fetched_at":27},"cleanup-duplicate-meta","Cleanup Duplicate Meta","1.0.2","Tonya Mork","https:\u002F\u002Fprofiles.wordpress.org\u002Fhellofromtonya\u002F","\u003Cp>There are times when your database gets filled up with duplicate entries that you may not want.  Cleanup Duplicate Meta allows you to check for any duplicates in either the Post Meta or User Meta tables.  Then if you want to get rid of them, simply click on the Cleanup button and Cleanup Duplicate Meta deletes the duplicates leaving either the first or last meta (you select which).\u003C\u002Fp>\n\u003Cp>The interface is simple and easy to use:\u003C\u002Fp>\n\u003Col>\n\u003Cli>‘Check for Duplicates’ queries the database and then displays all the duplicates found.\u003C\u002Fli>\n\u003Cli>‘Count Duplicates’ counts all the duplicates found in the database (i.e. a total count).\u003C\u002Fli>\n\u003Cli>The ‘Cleanup’ buttons trigger a SQL query to run, which deletes each of the duplicate entries, leaving either the first or last one (per your selection) in the database.  All non-duplicates remain untouched by the plugin.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>See the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fcleanup-duplicate-meta\u002Fscreenshots\u002F\" rel=\"ugc\">screenshots tab\u003C\u002Fa> for more details.\u003C\u002Fp>\n","Cleanup Duplicate Meta gives you a tool to check for and delete duplicate Post and\u002For User Meta entries in the database tables.",200,9629,11,"2015-05-09T11:17:00.000Z","4.2.39","3.5",[115,116,117,22,23],"database-cleanup","duplicate-meta","meta","http:\u002F\u002Fwpdevelopersclub.com\u002Fwordpress-plugins\u002Fcleanup-duplicate-meta\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcleanup-duplicate-meta.1.0.2.zip",{"slug":121,"name":122,"version":123,"author":124,"author_profile":125,"description":126,"short_description":127,"active_installs":108,"downloaded":128,"rating":129,"num_ratings":91,"last_updated":130,"tested_up_to":131,"requires_at_least":132,"requires_php":74,"tags":133,"homepage":136,"download_link":137,"security_score":25,"vuln_count":13,"unpatched_count":13,"last_vuln_date":26,"fetched_at":27},"metabase-post-user-meta-editor","Metabase – Post & User Meta Editor","0.8.1","David Towoju","https:\u002F\u002Fprofiles.wordpress.org\u002Fdavexpression\u002F","\u003Cp>This plugin shows the post meta and user meta of your website. Post meta of custom post types can also be viewed. Only admins can view this meta data.\u003C\u002Fp>\n\u003Cspan class=\"embed-youtube\" style=\"text-align:center; display: block;\">\u003Ciframe loading=\"lazy\" class=\"youtube-player\" width=\"750\" height=\"422\" src=\"https:\u002F\u002Fwww.youtube.com\u002Fembed\u002FT0EXphFEcqo?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent\" allowfullscreen=\"true\" style=\"border:0;\" sandbox=\"allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox\">\u003C\u002Fiframe>\u003C\u002Fspan>\n\u003Ch3>Post Meta\u003C\u002Fh3>\n\u003Cp>All user meta data can be viewed with this plugin (Metabase) – including custom post types. Both public and private meta keys can be viewed. Private meta keys start with the underscore prefix and are not meant to be seen in the admin.\u003C\u002Fp>\n\u003Cp>In short, any data that can be viewed with \u003Ccode>get_post_meta()\u003C\u002Fcode> can be viewed with this plugin.\u003C\u002Fp>\n\u003Cp>To view your post meta, please go to the open the post in the WP Admin and scroll down to end of the page, you will see a table titled “Meta”.\u003C\u002Fp>\n\u003Ch3>User Meta\u003C\u002Fh3>\n\u003Cp>All user meta data can be viewed\u002Fmanaged with this plugin (Metabase). Also, private and public meta keys can be viewed. Any data that can be viewed with \u003Ccode>get_user_meta()\u003C\u002Fcode> can be viewed with this plugin.\u003C\u002Fp>\n\u003Cp>To view your plugin, please got to the Users page and click to view a user. Scroll down and you will see the\u003C\u002Fp>\n\u003Ch3>Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Free\u003C\u002Fli>\n\u003Cli>Stand-alone, no need to install any other plugin for this to work\u003C\u002Fli>\n\u003Cli>Delete meta data\u003C\u002Fli>\n\u003Cli>View private meta data\u003C\u002Fli>\n\u003Cli>Edit and change the values of your meta data\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Getting Started\u003C\u002Fh3>\n\u003Cp>After installing this plugin, a metabox will be added to your posts and users.\u003C\u002Fp>\n\u003Cp>You can filter the post types you want the metabox to appear in.\u003C\u002Fp>\n","Manage post meta, custom post type meta and user meta of your WordPress site.",4026,80,"2025-04-04T06:12:00.000Z","6.5.8","5.0",[117,22,134,135,23],"show-post-meta","show-user-meta","https:\u002F\u002Fpluginette.com\u002Fproduct\u002Fmetabase\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fmetabase-post-user-meta-editor.0.8.1.zip",{"attackSurface":139,"codeSignals":162,"taintFlows":194,"riskAssessment":195,"analyzedAt":206},{"hooks":140,"ajaxHandlers":158,"restRoutes":159,"shortcodes":160,"cronEvents":161,"entryPointCount":13,"unprotectedCount":13},[141,147,151,155],{"type":142,"name":143,"callback":144,"file":145,"line":146},"action","plugins_loaded","metaviewer_load_textdomain","metaviewer.php",24,{"type":142,"name":148,"callback":149,"file":145,"line":150},"add_meta_boxes","metaviewer_add_meta_box",47,{"type":142,"name":152,"callback":153,"file":145,"line":154},"show_user_profile","metaviewer_show_user_meta",160,{"type":142,"name":156,"callback":153,"file":145,"line":157},"edit_user_profile",161,[],[],[],[],{"dangerousFunctions":163,"sqlUsage":168,"outputEscaping":170,"fileOperations":13,"externalRequests":13,"nonceChecks":13,"capabilityChecks":91,"bundledLibraries":193},[164],{"fn":165,"file":145,"line":166,"context":167},"unserialize",54,"$data = @unserialize( $value );",{"prepared":13,"raw":13,"locations":169},[],{"escaped":171,"rawEcho":172,"locations":173},6,9,[174,177,179,181,183,185,187,189,191],{"file":145,"line":175,"context":176},74,"raw output",{"file":145,"line":178,"context":176},81,{"file":145,"line":180,"context":176},82,{"file":145,"line":182,"context":176},83,{"file":145,"line":184,"context":176},124,{"file":145,"line":186,"context":176},127,{"file":145,"line":188,"context":176},133,{"file":145,"line":190,"context":176},134,{"file":145,"line":192,"context":176},135,[],[],{"summary":196,"deductions":197},"The 'metaviewer-debug-meta-data' plugin v1.0.0 presents a mixed security posture. On the positive side, it exhibits no known historical vulnerabilities (CVEs) and its static analysis shows a very limited attack surface with no directly exposed AJAX handlers, REST API routes, shortcodes, or cron events. Furthermore, all SQL queries are correctly handled with prepared statements. However, the presence of the `unserialize` function is a significant concern. While no taint flows were detected, `unserialize` can be a gateway to remote code execution if it processes untrusted input. The plugin also demonstrates a concerning lack of output escaping, with only 40% of outputs being properly escaped, leaving it vulnerable to cross-site scripting (XSS) attacks. The absence of nonce checks and the limited capability checks further reduce its security robustness, especially considering the potential risk posed by `unserialize`.",[198,201,204],{"reason":199,"points":200},"Use of unserialize function",15,{"reason":202,"points":203},"Low percentage of properly escaped output",8,{"reason":205,"points":70},"No nonce checks detected","2026-03-17T01:45:22.123Z",{"wat":208,"direct":213},{"assetPaths":209,"generatorPatterns":210,"scriptPaths":211,"versionParams":212},[],[],[],[],{"cssClasses":214,"htmlComments":216,"htmlAttributes":217,"restEndpoints":218,"jsGlobals":219,"shortcodeOutput":220},[215],"metaviewer-wrapper",[],[],[],[],[]]