[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f10ij47RB-5_dn5so2ggXt38Z7Z4Mwrl3qLqzaY2ZzmY":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":25,"download_link":26,"security_score":27,"vuln_count":28,"unpatched_count":29,"last_vuln_date":30,"fetched_at":31,"vulnerabilities":32,"developer":62,"crawl_stats":38,"alternatives":69,"analysis":182,"fingerprints":307},"sql-chart-builder","SQL Chart Builder","2.3.7.2","Guaven Labs","https:\u002F\u002Fprofiles.wordpress.org\u002Felvinhaci\u002F","\u003Cp>The plugin can create beautiful charts based on your SQL queries, then you can use those charts in any part of your website.\u003Cbr \u002F>\nYou can use both native wp and non-wp mysql tables in your queries.\u003C\u002Fp>\n\u003Ch3>Pie chart, Donut chart, Line chart, Bar chart, Column chart, Area chart\u003C\u002Fh3>\n\u003Ch4>How to use\u003C\u002Fh4>\n\u003Col>\n\u003Cli>\n\u003Cp>Give any name to your report.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Use our preinstalled chart or create new one yourself: choose desired chart type, type sql query,\u003Cbr \u002F>\nenter field names, labels and then press to Publish\u002FUpdate\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>You can use multiple SQL queries too. Just split them by ; sign. You can also add shortcode argument to SQL query. For example if you\u003Cbr \u002F>\ntype “select * from wp_posts where ID>{arg1}” then it you can pass arg1 value to the query with  [gvn_schart_2 id=”2″ arg1=”11″] shortcode.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>After update\u002Fsave you will see needed shortcode below there. You can use that shortcode anywhere in your website: in pages, posts, widgets etc.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Just check “Show table-view data below the graph” in order to get table-list view below each chart.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Using “Dynamic Filters” you can create dynamic variables inside SQL code. It also creates corresponding dynamic input form above each chart.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Dynamic filters\u003C\u002Fh4>\n\u003Cp>Use this format: variable_name~default_value~variable_label~variable_type | variable_name~default_value~variable_label~variable_type etc.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>variable_name – any single name you want.\u003C\u002Fli>\n\u003Cli>default_value – default value when no any variable chosen by a user\u003C\u002Fli>\n\u003Cli>variable_label – Label which would be visible at a form above the chart\u003C\u002Fli>\n\u003Cli>variable_type – number, text or date\u003C\u002Fli>\n\u003Cli>~ is a separator between variable elements.\u003C\u002Fli>\n\u003Cli>| is a separator between variables\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>For example if to put\u003C\u002Fp>\n\u003Cp>limit_tag~10~Count~number | post_date_tag~2010-07-05 17:25:18~Date Published~date,\u003C\u002Fp>\n\u003Cp>then you can use this SQL code\u003C\u002Fp>\n\u003Cp>select * from wp_posts where post_date\u003C{post_date_tag} limit {limit_tag}\u003C\u002Fp>\n\u003Cp>in SQL CODE field.\u003Cbr \u002F>\n{post_date_tag} and {limit_tag} would be replaced with dynamic variables.\u003C\u002Fp>\n\u003Cp>So, the plugin will automatically recognize it and put corresponding selectboxes above the chart.\u003C\u002Fp>\n\u003Ch4>Website\u003C\u002Fh4>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fguaven.com\u002Fmy-sql-charts\u002F\" rel=\"nofollow ugc\">https:\u002F\u002Fguaven.com\u002Fmy-sql-charts\u002F\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch4>Documentation\u003C\u002Fh4>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fguaven.com\u002Fmy-sql-charts\u002F#docs\" rel=\"nofollow ugc\">https:\u002F\u002Fguaven.com\u002Fmy-sql-charts\u002F#docs\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch4>Bug Submission and Forum Support\u003C\u002Fh4>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fguaven.com\u002Fcontact\u002Fsolution-request\u002F\" rel=\"nofollow ugc\">Contact Page\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch4>Please Vote if you liked our plugin\u003C\u002Fh4>\n\u003Cp>Your votes really helps us. Thanks.\u003C\u002Fp>\n\u003Ch3>Available Filters\u003C\u002Fh3>\n\u003Cp>apply_filters( ‘guaven_sqlcharts_table_empty_cell’);\u003C\u002Fp>\n\u003Cp>apply_filters(‘guaven_sqlcharts_pre_print_vars’);\u003C\u002Fp>\n\u003Cp>apply_filters( ‘guaven_sqlcharts_final_output’);\u003C\u002Fp>\n\u003Cp>apply_filters(‘guaven_sqlcharts_rendered_sql’);\u003C\u002Fp>\n","Turn Your SQL Queries to Beautiful Dynamic Charts- Pie, Line, Area, Donut, Bar Charts with date\u002Finput filters.",600,31868,78,21,"2026-03-13T07:00:00.000Z","6.9.4","5.0.0","",[20,21,22,23,24],"charts","mysql","sql","sql-chart","visualizer","http:\u002F\u002Fguaven.com\u002Fupdatepusher","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsql-chart-builder.2.3.8.zip",77,2,1,"2025-09-22 00:00:00","2026-03-15T15:16:48.613Z",[33,47],{"id":34,"url_slug":35,"title":36,"description":37,"plugin_slug":4,"theme_slug":38,"affected_versions":39,"patched_in_version":38,"severity":40,"cvss_score":41,"cvss_vector":42,"vuln_type":43,"published_date":30,"updated_date":44,"references":45,"days_to_patch":38},"CVE-2025-58233","sql-chart-builder-authenticated-contributor-stored-cross-site-scripting","SQL Chart Builder \u003C= 2.3.7.2 - Authenticated (Contributor+) Stored Cross-Site Scripting","The SQL Chart Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 2.3.7.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.",null,"\u003C=2.3.7.2","medium",6.4,"CVSS:3.1\u002FAV:N\u002FAC:L\u002FPR:L\u002FUI:N\u002FS:C\u002FC:L\u002FI:L\u002FA:N","Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')","2025-09-26 17:35:51",[46],"https:\u002F\u002Fwww.wordfence.com\u002Fthreat-intel\u002Fvulnerabilities\u002Fid\u002Fac00d82b-4095-4c0c-8b5c-ecff9fa67067?source=api-prod",{"id":48,"url_slug":49,"title":50,"description":51,"plugin_slug":4,"theme_slug":38,"affected_versions":52,"patched_in_version":53,"severity":40,"cvss_score":54,"cvss_vector":55,"vuln_type":56,"published_date":57,"updated_date":58,"references":59,"days_to_patch":61},"CVE-2024-11430","sql-chart-builder-authenticated-contributor-sql-injection","SQL Chart Builder \u003C= 2.3.6 - Authenticated (Contributor+) SQL Injection","The SQL Chart Builder plugin for WordPress is vulnerable to SQL Injection via the 'arg1' arg of the 'gvn_schart_2' shortcode in all versions up to, and including, 2.3.6 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query.  This makes it possible for authenticated attackers, with Contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.","\u003C=2.3.6","2.3.7",6.5,"CVSS:3.1\u002FAV:N\u002FAC:L\u002FPR:L\u002FUI:N\u002FS:U\u002FC:H\u002FI:N\u002FA:N","Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')","2024-12-11 15:19:02","2025-11-05 19:02:52",[60],"https:\u002F\u002Fwww.wordfence.com\u002Fthreat-intel\u002Fvulnerabilities\u002Fid\u002F1f818aad-8d05-4665-a7dc-50bc56cbde5f?source=api-prod",329,{"slug":63,"display_name":7,"profile_url":8,"plugin_count":64,"total_installs":65,"avg_security_score":66,"avg_patch_time_days":61,"trust_score":67,"computed_at":68},"elvinhaci",5,700,91,73,"2026-04-04T04:57:31.174Z",[70,93,113,138,161],{"slug":71,"name":72,"version":73,"author":74,"author_profile":75,"description":76,"short_description":77,"active_installs":78,"downloaded":79,"rating":13,"num_ratings":80,"last_updated":81,"tested_up_to":82,"requires_at_least":83,"requires_php":84,"tags":85,"homepage":88,"download_link":89,"security_score":90,"vuln_count":28,"unpatched_count":91,"last_vuln_date":92,"fetched_at":31},"wp-business-intelligence-lite","WP Business Intelligence Lite","3.2.0","joeyoungblood","https:\u002F\u002Fprofiles.wordpress.org\u002Fjoeyoungblood\u002F","\u003Cp>WP Business Intelligence Lite allows you to powerfully display responsive data tables and charts on your website. This plugin is simple to use and allows you to connect with your wordpress database and display the data in real time. Once you have created at least one SQL query that retrieves data from your DB, you can define the type of chart (bar, donut, line, or grouped bar) or table to be used to display them. A simple shortcode embeds the chart or table in any post or page. Each page refresh retrieves the data from the DB so that the information in the chart or table is always up-to-date.\u003C\u002Fp>\n\u003Cp>Installation guide, FAQs and support can be found at \u003Ca href=\"http:\u002F\u002Fwww.wpbusinessintelligence.com\u002Fsupport\" rel=\"nofollow ugc\">WP Business Intelligence Support\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"http:\u002F\u002Fwww.wpbusinessintelligence.com\u002Fdemos\" rel=\"nofollow ugc\">WP Business Intelligence Demos\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>In order to use your own live MySQL, MS SQL, or PostgreSQL database with WP Business Intelligence, purchase the Pro version of WP Business Intelligence from the \u003Ca href=\"http:\u002F\u002Fwww.wpbusinessintelligence.com\" rel=\"nofollow ugc\">WP Business Intelligence web site\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>We are actively developing this plugin and would love to hear from you with feature requests. \u003Ca href=\"http:\u002F\u002Fwww.wpbusinessintelligence.com\u002Fcontact\u002F\" rel=\"nofollow ugc\">Contact Us.\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>Some icons provided by \u003Ca href=\"https:\u002F\u002Ffontawesome.com\u002Flicense\" rel=\"nofollow ugc\">Font Awesome\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Col>\n\u003Cli>Live connection to your WordPress DB via custom SQL queries\u003C\u002Fli>\n\u003Cli>Responsive charts\u002Ftables\u003C\u002Fli>\n\u003Cli>Works in Chrome, Firefox, IE9+\u003C\u002Fli>\n\u003Cli>Charts based on \u003Ca href=\"https:\u002F\u002Feventbrite.github.io\u002Fbritecharts\u002Ftutorial-kitchen-sink.html\" rel=\"nofollow ugc\">Britecharts\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Tables build on \u003Ca href=\"https:\u002F\u002Fdatatables.net\u002F\" rel=\"nofollow ugc\">Datatables\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Fol>\n","Dynamic web charts and tables for your site! Connect to your live WordPress instance DB to retrieve data in real-time and update charts and tables!",70,30161,10,"2023-01-01T04:53:00.000Z","6.1.10","4.4.0","5.6.0",[20,86,21,22,87],"d3","tables","http:\u002F\u002Fwww.wpbusinessintelligence.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-business-intelligence-lite.3.2.0.zip",81,0,"2015-04-01 00:00:00",{"slug":94,"name":95,"version":96,"author":97,"author_profile":98,"description":99,"short_description":100,"active_installs":80,"downloaded":101,"rating":102,"num_ratings":28,"last_updated":103,"tested_up_to":104,"requires_at_least":105,"requires_php":18,"tags":106,"homepage":110,"download_link":111,"security_score":112,"vuln_count":91,"unpatched_count":91,"last_vuln_date":38,"fetched_at":31},"display-sql-stats","Display SQL Stats","0.9.5.1","Juergen Schulze","https:\u002F\u002Fprofiles.wordpress.org\u002F1manfactory\u002F","\u003Cp>! ! !  S T I L L   B E T A  ! ! !\u003C\u002Fp>\n\u003Cp>Displaying SQL result data as graphical chart on your blog (shortcodes) or your dashboard with use of Google Chart Tools.\u003C\u002Fp>\n\u003Ch3>Remove plugin\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Deactivate plugin through the ‘Plugins’ menu in WordPress\u003C\u002Fli>\n\u003Cli>Delete plugin through the ‘Plugins’ menu in WordPress\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>It’s best to use the build in delete function of wordpress. That way all the stored data will be removed and no orphaned data will stay.\u003C\u002Fp>\n\u003Ch3>To do\u003C\u002Fh3>\n\u003Cp>More translations. Does someone wants to help?\u003C\u002Fp>\n","! ! !  S T I L L   B E T A  ! ! !",5312,100,"2017-05-15T14:22:00.000Z","4.7.32","2.7",[107,20,108,109,21],"chart","google-chart","google-chart-tools","http:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdisplay-sql-stats\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdisplay-sql-stats.zip",85,{"slug":114,"name":115,"version":116,"author":117,"author_profile":118,"description":119,"short_description":120,"active_installs":121,"downloaded":122,"rating":123,"num_ratings":124,"last_updated":125,"tested_up_to":126,"requires_at_least":127,"requires_php":128,"tags":129,"homepage":133,"download_link":134,"security_score":135,"vuln_count":136,"unpatched_count":91,"last_vuln_date":137,"fetched_at":31},"wp-db-backup","Database Backup for WordPress","2.5.2","WP Engine","https:\u002F\u002Fprofiles.wordpress.org\u002Fwpengine\u002F","\u003Cp>Backup your database instantly, send the backup via email, or schedule backups to run automatically.\u003C\u002Fp>\n\u003Cp>Database Backup for WordPress allows you to quickly back up your core WordPress database tables, and either download the backup as a gzipped file, or send it via email to an address you choose.\u003C\u002Fp>\n\u003Cp>By default, the plugin will always back up all the core WordPress database tables. However, you may also selectively back up any custom tables that might be created by other plugins\u003C\u002Fp>\n\u003Cp>Additional options include the ability to exclude spam comments from the comments table, or post revisions from the posts table, saving you space and bandwidth.\u003C\u002Fp>\n\u003Cp>You can also enable scheduled backups to run automatically at set intervals, and configure the email address to send the scheduled backups to.\u003C\u002Fp>\n\u003Ch4>Backup Before You Mess Up\u003C\u002Fh4>\n\u003Cp>Backups are the one thing you don’t think of until you need them. You might have the best web host, the most secure server, and a tried and tested process for running plugin, theme, or core updates. But all it takes is one little thing to go wrong, and you lose your entire website.\u003C\u002Fp>\n\u003Cp>You need a reliable and automated solution which backs up your WordPress data and sends it to an off-site location. Database Backup for WordPress is that solution.\u003C\u002Fp>\n\u003Ch4>Why You Should Back Up Your Website\u003C\u002Fh4>\n\u003Cp>As much planning as you do, any CMS like WordPress that stores its data in a database is vulnerable. Hardware, software, and security hiccups are rare, but they do happen. Even the best enterprise systems in the world have multiple levels of backup in place.\u003C\u002Fp>\n\u003Cp>Think about the data you store in your WordPress site. Your blog posts since the day you launched the site. Your customers, products, and order history if you run an ecommerce site. Backups are like implementing an insurance policy for your data. With backups, you have a reliable way of restoring that data if anything goes wrong.\u003C\u002Fp>\n\u003Cp>Simple, automated backups save you time and give you peace of mind that you are prepared for the worst case scenario, even if you never need it. Better to have it and not need it, than to not have it and suddenly need it.\u003C\u002Fp>\n\u003Ch4>Scheduled Backups\u003C\u002Fh4>\n\u003Cp>Depending on your needs, you might want to back up your database every few minutes, hourly, daily, weekly, or monthly. You’ll want to automate this process, or it becomes another possible point of failure.\u003C\u002Fp>\n\u003Cp>Scheduled backups give you peace of mind that your data is being backed up as much or as little as you need, without your intervention. By emailing the backups to an email address you choose, you can verify that the backup has run, and store it in a safe location.\u003C\u002Fp>\n\u003Ch3>Translators\u003C\u002Fh3>\n\u003Cp>Thanks to the following people for providing translation files for Database Backup for WordPress:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Abel Cheung\u003C\u002Fli>\n\u003Cli>Alejandro Urrutia\u003C\u002Fli>\n\u003Cli>Alexander Kanakaris\u003C\u002Fli>\n\u003Cli>Angelo Andrea Iorio\u003C\u002Fli>\n\u003Cli>Calle\u003C\u002Fli>\n\u003Cli>Daniel Erb\u003C\u002Fli>\n\u003Cli>Daniel Villoldo\u003C\u002Fli>\n\u003Cli>Diego Pierotto\u003C\u002Fli>\n\u003Cli>Eilif Nordseth\u003C\u002Fli>\n\u003Cli>Eric Lassauge\u003C\u002Fli>\n\u003Cli>Friedlich\u003C\u002Fli>\n\u003Cli>Gilles Wittezaele\u003C\u002Fli>\n\u003Cli>Icemanpro\u003C\u002Fli>\n\u003Cli>İzzet Emre Erkan\u003C\u002Fli>\n\u003Cli>Jong-In Kim\u003C\u002Fli>\n\u003Cli>Kaveh\u003C\u002Fli>\n\u003Cli>Kessia Pinheiro\u003C\u002Fli>\n\u003Cli>Kuratkoo\u003C\u002Fli>\n\u003Cli>Majed Alotaibi\u003C\u002Fli>\n\u003Cli>Michał Gołuński\u003C\u002Fli>\n\u003Cli>Michele Spagnuolo\u003C\u002Fli>\n\u003Cli>Paopao\u003C\u002Fli>\n\u003Cli>Philippe Galliard\u003C\u002Fli>\n\u003Cli>Robert Buj\u003C\u002Fli>\n\u003Cli>Roger\u003C\u002Fli>\n\u003Cli>Rune Gulbrandsøy\u003C\u002Fli>\n\u003Cli>Serge Rauber\u003C\u002Fli>\n\u003Cli>Sergey Biryukov\u003C\u002Fli>\n\u003Cli>Tai\u003C\u002Fli>\n\u003Cli>Timm Severin\u003C\u002Fli>\n\u003Cli>Tzafrir Rehan\u003C\u002Fli>\n\u003Cli>吴曦\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Past Contributors\u003C\u002Fh3>\n\u003Cp>filosofo, skippy, Firas, LaughingLizard, MtDewVirus, Podz, Ringmaster\u003C\u002Fp>\n","Database Backup for WordPress is your one-stop database backup solution for WordPress.",70000,3731269,90,66,"2022-05-26T11:49:00.000Z","6.0.11","3.6.0","5.3",[130,131,132,21],"backup","database","database-backup","https:\u002F\u002Fgithub.com\u002Fdeliciousbrains\u002Fwp-db-backup","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-db-backup.2.5.2.zip",82,4,"2022-05-11 00:00:00",{"slug":139,"name":140,"version":141,"author":142,"author_profile":143,"description":144,"short_description":145,"active_installs":146,"downloaded":147,"rating":148,"num_ratings":148,"last_updated":149,"tested_up_to":16,"requires_at_least":150,"requires_php":151,"tags":152,"homepage":157,"download_link":158,"security_score":159,"vuln_count":29,"unpatched_count":91,"last_vuln_date":160,"fetched_at":31},"index-wp-mysql-for-speed","Index WP MySQL For Speed","1.5.6","OllieJones","https:\u002F\u002Fprofiles.wordpress.org\u002Folliejones\u002F","\u003Ch4>How do I use this plugin?\u003C\u002Fh4>\n\u003Cp>After you install and activate this plugin, visit the Index MySQL Tool under the Tools menu. From there you can press the \u003Cem>Add Keys Now\u003C\u002Fem> button. If you have large tables, use it with \u003Ca href=\"https:\u002F\u002Fwp-cli.org\u002F\" rel=\"nofollow ugc\">WP-CLI\u003C\u002Fa> instead to avoid timeouts. See the WP-CLI section to learn more.\u003C\u002Fp>\n\u003Ch4>What does it do for my site?\u003C\u002Fh4>\n\u003Cp>This plugin works to make your MySQL database work more efficiently by adding high-performance keys to the tables you choose. On request it monitors your site’s use of your MySQL database to detect which database operations are slowest. It is most useful for large sites: sites with many users, posts, pages, and \u002F or products.\u003C\u002Fp>\n\u003Cp>You can use it to restore WordPress’s default keys if need be.\u003C\u002Fp>\n\u003Ch4>What is this all about?\u003C\u002Fh4>\n\u003Cp>Where does WordPress store all that stuff that makes your site great? Where are your pages, posts, products, media, users, custom fields, metadata, and all your valuable content? All that data is in the \u003Ca href=\"https:\u002F\u002Fwww.mysql.com\u002F\" rel=\"nofollow ugc\">MySQL\u003C\u002Fa> relational database management system. (Many hosting providers and servers use the \u003Ca href=\"https:\u002F\u002Fmariadb.org\u002F\" rel=\"nofollow ugc\">MariaDB\u003C\u002Fa> fork of the MySQL software; it works exactly the same way as MySQL itself.)\u003C\u002Fp>\n\u003Cp>As your site grows, your MySQL tables grow. Giant tables can make your page loads slow down, frustrate your users, and even hurt your search-engine rankings. And, bulk imports can take absurd amounts of time. What can you do about this?\u003C\u002Fp>\n\u003Cp>You can install and use a database cleaner plugin to get rid of old unwanted data and reorganize your tables. That makes them smaller, and therefore faster. That is a good and necessary task. That is not the task of this plugin. You can, if your hosting provider supports it, install and use a \u003Ca href=\"https:\u002F\u002Fdeveloper.wordpress.org\u002Freference\u002Fclasses\u002Fwp_object_cache\u002F#persistent-cache-plugins\" rel=\"nofollow ugc\">Persistent Object Cache plugin\u003C\u002Fa> to reduce traffic to your database. That is not the task of this plugin either.\u003C\u002Fp>\n\u003Cp>This plugin adds database \u003Ca href=\"https:\u002F\u002Fdev.mysql.com\u002Fdoc\u002Frefman\u002F8.0\u002Fen\u002Fmysql-indexes.html\" rel=\"nofollow ugc\">keys\u003C\u002Fa> (also called indexes) to your MySQL tables to make it easier for WordPress to find the information it needs. All relational database management systems store your information in long-lived \u003Cem>tables\u003C\u002Fem>. For example, WordPress stores your posts and other content in a table called \u003Cem>wp_posts\u003C\u002Fem>, and custom post fields in another table called \u003Cem>wp_postmeta\u003C\u002Fem>.  A successful site can have thousands of posts and hundreds of thousands of custom post fields. MySQL has two jobs:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Keep all that data organized.\u003C\u002Fli>\n\u003Cli>Find the data it needs quickly.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>To do its second job, MySQL uses database keys. Each table has one or more keys. For example, \u003Ccode>wp_posts\u003C\u002Fcode> has a key to let it quickly find posts when you know the author. Without its \u003Cem>post_author\u003C\u002Fem> key MySQL would have to scan every one of your posts looking for matches to the author you want. Our users know what that looks like: slow. With the key, MySQL can jump right to the matching posts.\u003C\u002Fp>\n\u003Cp>In a new WordPress site with a couple of users and a dozen posts, the keys don’t matter very much. As the site grows the keys start to matter, a lot. Database management systems are designed to have their keys updated, adjusted, and tweaked as their tables grow. They’re designed to allow the keys to evolve without changing the content of the underlying tables. In organizations with large databases adding, dropping, or altering keys doesn’t change the underlying data. It is a routine maintenance task in many data centers. If changing keys caused databases to lose data, the MySQL and MariaDB developers would hear howling not just from you and me, but from many heavyweight users. (You should still back up your WordPress instance of course.)\u003C\u002Fp>\n\u003Cp>Better keys allow WordPress’s code to run faster \u003Cem>without any code changes\u003C\u002Fem>.  Experience with large sites shows that many MySQL slowdowns can be improved by better keys. Code is poetry, data is treasure, and database keys are grease that makes code and data work together smoothly.\u003C\u002Fp>\n\u003Ch4>Which tables does the plugin add keys to?\u003C\u002Fh4>\n\u003Cp>This plugin adds and updates keys in these WordPress and WooCommerce tables.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>wp_comments\u003C\u002Fli>\n\u003Cli>wp_commentmeta\u003C\u002Fli>\n\u003Cli>wp_posts\u003C\u002Fli>\n\u003Cli>wp_postmeta\u003C\u002Fli>\n\u003Cli>wp_termmeta\u003C\u002Fli>\n\u003Cli>wp_users\u003C\u002Fli>\n\u003Cli>wp_usermeta\u003C\u002Fli>\n\u003Cli>wp_options\u003C\u002Fli>\n\u003Cli>wp_wc_orders_meta\u003C\u002Fli>\n\u003Cli>wp_woocommerce_order_itemmeta\u003C\u002Fli>\n\u003Cli>wp_automatewoo_log_meta\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>You only need run this plugin once to get its benefits.\u003C\u002Fp>\n\u003Ch4>How can I monitor my database’s operation?\u003C\u002Fh4>\n\u003Cp>On the Index MySQL page (from your Tools menu on your dashboard), you will find the “Monitor Database Operations” tab. Use it to request monitoring for a number of minutes you choose.\u003C\u002Fp>\n\u003Cp>You can monitor\u003C\u002Fp>\n\u003Cul>\n\u003Cli>either the site (your user-visible pages) or the dashboard, or both.\u003C\u002Fli>\n\u003Cli>all pageviews, or a random sample. (Random samples are useful on very busy sites to reduce monitoring overhead.)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Once you have gathered monitoring information, you can view the captured queries, and sort them by how long they take. Or you can save the monitor information to a file and show it to somebody who knows about database operations. Or you can upload the monitor to the plugin’s servers so the authors can look at it.\u003C\u002Fp>\n\u003Cp>It’s a good idea to monitor for a five-minute interval at a time of day when your site is busy. Once you’ve completed a monitor, you can examine it to determine which database operations are slowing you down the most.\u003C\u002Fp>\n\u003Cp>Please consider uploading your saved monitors to the plugin’s servers. It’s how we learn from your experience to keep improving. Push the Upload button on the monitor’s tab.\u003C\u002Fp>\n\u003Ch4>WP-CLI command line operation\u003C\u002Fh4>\n\u003Cp>This plugin supports \u003Ca href=\"https:\u002F\u002Fwp-cli.org\u002F\" rel=\"nofollow ugc\">WP-CLI\u003C\u002Fa>.  When your tables are large this is the best way to add the high-performance keys: it doesn’t time out.\u003C\u002Fp>\n\u003Cp>Give the command \u003Ccode>wp help index-mysql\u003C\u002Fcode> for details. A few examples:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>wp index-mysql status\u003C\u002Fcode> shows the current status of high-performance keys.\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp index-mysql enable --all\u003C\u002Fcode> adds the high-performance keys to all tables that don’t have them.\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp index-mysql enable wp_postmeta\u003C\u002Fcode> adds the high-performance keys to the postmeta table.\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp index-mysql disable --all\u003C\u002Fcode> removes the high-performance keys from all tables that have them, restoring WordPress’s default keys.\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp index-mysql enable --all --dryrun\u003C\u002Fcode> writes out the SQL statements necessary to add the high-performance keys to all tables, but does not run them.\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp index-mysql enable --all --dryrun | wp db query\u003C\u002Fcode> writes out the SQL statements and pipes them to wp db to run them.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Note: avoid saving the –dryrun output statements to run later. The plugin generates them to match the current state of your tables.\u003C\u002Fp>\n\u003Ch4>Why use this plugin?\u003C\u002Fh4>\n\u003Cp>Three reasons (maybe four):\u003C\u002Fp>\n\u003Col>\n\u003Cli>to save carbon footprint.\u003C\u002Fli>\n\u003Cli>to save carbon footprint.\u003C\u002Fli>\n\u003Cli>to save carbon footprint.\u003C\u002Fli>\n\u003Cli>to save people time.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Seriously, the microwatt hours of electricity saved by faster web site technologies add up fast, especially at WordPress’s global scale.\u003C\u002Fp>\n\u003Ch4>How can I learn more about making my WordPress site more efficient?\u003C\u002Fh4>\n\u003Cp>We offer several plugins to help with your site’s database efficiency. You can \u003Ca href=\"https:\u002F\u002Fwww.plumislandmedia.net\u002Fwordpress\u002Fperformance\u002Foptimizing-wordpress-database-servers\u002F\" rel=\"nofollow ugc\">read about them here\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch4>Credits\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Michael Uno for Admin Page Framework.\u003C\u002Fli>\n\u003Cli>Marco Cesarato for LiteSQLParser.\u003C\u002Fli>\n\u003Cli>Allan Jardine for Datatables.net.\u003C\u002Fli>\n\u003Cli>Leho Kraav and Sebastian Sommer for suggesting the WooCommerce tables.\u003C\u002Fli>\n\u003Cli>Japreet Sethi for advice, and for testing on his large installation.\u003C\u002Fli>\n\u003Cli>Rick James for everything.\u003C\u002Fli>\n\u003Cli>Jetbrains for their IDE tools, especially PhpStorm. It’s hard to imagine trying to navigate an epic code base without their tools.\u003C\u002Fli>\n\u003C\u002Ful>\n","Speed up your WordPress site by adding high-performance keys (database indexes) to your MariaDB \u002F MySQL database tables.",50000,645309,96,"2026-01-26T20:00:00.000Z","4.2","5.6",[153,154,21,155,156],"index","key","performance","wp-cli","https:\u002F\u002Fplumislandmedia.org\u002Findex-wp-mysql-for-speed\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Findex-wp-mysql-for-speed.1.5.6.zip",99,"2024-06-22 00:00:00",{"slug":162,"name":163,"version":164,"author":165,"author_profile":166,"description":167,"short_description":168,"active_installs":146,"downloaded":169,"rating":170,"num_ratings":171,"last_updated":172,"tested_up_to":173,"requires_at_least":174,"requires_php":18,"tags":175,"homepage":179,"download_link":180,"security_score":159,"vuln_count":28,"unpatched_count":91,"last_vuln_date":181,"fetched_at":31},"wp-phpmyadmin-extension","WP phpMyAdmin","5.2.2.01","Puvox Software","https:\u002F\u002Fprofiles.wordpress.org\u002Fpuvoxsoftware\u002F","\u003Ch4>[ ✅ 𝐒𝐄𝐂𝐔𝐑𝐄 𝐏𝐋𝐔𝐆𝐈𝐍𝐒 𝐵𝓎 𝒫𝓊𝓋𝑜𝓍 ] :\u003C\u002Fh4>\n\u003Cblockquote>\n\u003Cp>• Checked against vulnerability holes.\u003Cbr \u002F>\n  • No extra load\u002Fslowness to site.\u003Cbr \u002F>\n  • Does not collect & share private data.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch4>Plugin Description\u003C\u002Fh4>\n\u003Cp>The famous database browser & manager (for MySQL & MariaDB) – use it inside WordPress Dashboard without an extra hassle.\u003C\u002Fp>\n\u003Ch3>NOTES\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>This plugin has been started from 2018 year, and we have no connections to the old age’s vulnerable wp-phpMyAdmin plugin (published elsewhere by 3rd party scammers) . So, this current plugin is just a wrapper for official phpMyAdmin release and depends itself on the realiability & security of the \u003Ccode>phpMyAdmin\u003C\u002Fcode> itself. Also, initially we wanted to put PhpMyAdmin released \u003Ccode>.zip\u003C\u002Fcode> file untouched (to ensure the checksums are same) and unpack that \u003Ccode>.zip\u003C\u002Fcode> directly upon plugin’s installation, but unfortunately WordPress Plugin Team didn’t allow to put \u003Ccode>.zip\u003C\u002Fcode> file in the package (saying that SVN doesn’t like working with \u003Ccode>.zip\u003C\u002Fcode> files). Thus, we had to submit extracted PMA (but still original & untouched) to the repository.\u003C\u002Fli>\n\u003Cli>PHP >= 7.2.5 is required to for \u003Cstrong>phpMyAdmin\u003C\u002Fstrong> latest version (otherwise you will have option to use older version of PMA, which is not encouraged to be used).\u003C\u002Fli>\n\u003Cli>For the reason to make it compact, some unnecessary files (language files, OpenLayer\u002FGIS map lib, extra themes, etc) are removed.\u003C\u002Fli>\n\u003Cli>It’s recommended, that you enable the plugin only while you need to use PhpMyAdmin. Otherwise, for longer periods, you can deactivate plugin.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Liability\u003C\u002Fh4>\n\u003Cp>We are not developers of PhpMyAdmin itself, neither affiliated with them. We just made this plugin as a wrapper (container) of official PhpMyAdmin, to make it possible to be installed as a WP plugin. However, we don’t monitor PhpMyAdmin package’s source code itself. We take no responsibility about this plugin. Use it at your own responsibility (However, as it’s also visible in stats, thousands of users are using this extendion and only few people have complained about errors).\u003C\u002Fp>\n\u003Ch4>Available Options\u003C\u002Fh4>\n\u003Cp>See all available options and their description on plugin’s settings page.\u003C\u002Fp>\n","[ ✅ 𝐒𝐄𝐂𝐔𝐑𝐄 𝐏𝐋𝐔𝐆𝐈𝐍𝐒 𝐵𝓎 𝒫𝓊𝓋𝑜𝓍 ] phpMyAdmin -  Database Browser & Manager (for MySQL & MariaDB)",1055306,92,58,"2025-10-17T18:58:00.000Z","6.7.5","6.0",[131,176,21,177,178],"manager","phpminiadmin","phpmyadmin","https:\u002F\u002Fpuvox.software\u002Fsoftware\u002Fwordpress-plugins\u002F?plugin=wp-phpmyadmin-extension","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-phpmyadmin-extension.zip","2022-08-01 00:00:00",{"attackSurface":183,"codeSignals":254,"taintFlows":268,"riskAssessment":295,"analyzedAt":306},{"hooks":184,"ajaxHandlers":237,"restRoutes":243,"shortcodes":244,"cronEvents":252,"entryPointCount":253,"unprotectedCount":91},[185,191,194,198,201,204,206,210,214,217,221,226,229,232],{"type":186,"name":187,"callback":188,"file":189,"line":190},"action","admin_notices","guaven_sqlcharts_my_admin_notice","functions.php",98,{"type":186,"name":187,"callback":192,"file":189,"line":193},"guaven_sqlcharts_onboarding_notice",110,{"type":186,"name":195,"callback":196,"file":189,"line":197},"wp_enqueue_scripts","guaven_sqlcharts_enqueue_chart",133,{"type":186,"name":199,"callback":196,"file":189,"line":200},"admin_enqueue_scripts",134,{"type":186,"name":195,"callback":202,"file":189,"line":203},"guaven_sqlcharts_enqueue_main_style",140,{"type":186,"name":199,"callback":202,"file":189,"line":205},141,{"type":186,"name":207,"callback":208,"file":189,"line":209},"init","guaven_sqlcharts_register_post",150,{"type":186,"name":211,"callback":212,"file":189,"line":213},"admin_footer","guaven_sqlcharts_admin_front",172,{"type":186,"name":207,"callback":215,"file":189,"line":216},"guaven_register_gutenberg_blocks",243,{"type":186,"name":218,"callback":219,"priority":29,"file":189,"line":220},"save_post","guaven_sqlcharts_save_metabox_area",287,{"type":222,"name":223,"callback":224,"file":189,"line":225},"filter","the_content","closure",936,{"type":222,"name":227,"callback":224,"file":189,"line":228},"guaven_sqlcharts_table_empty_cell",963,{"type":222,"name":230,"callback":224,"file":189,"line":231},"guaven_sqlcharts_table_empty_value",964,{"type":186,"name":233,"callback":234,"priority":80,"file":235,"line":236},"woocommerce_order_status_completed","send_billink_workflow_request","guaven_sqlcharts.php",24,[238],{"action":239,"nopriv":240,"callback":239,"hasNonce":241,"hasCapCheck":240,"file":189,"line":242},"guaven_sqlcharts_onboarding_notice_dismissed",false,true,122,[],[245,249],{"tag":246,"callback":247,"file":189,"line":248},"gvn_schart_2","guaven_sqlcharts_local_shortcode",584,{"tag":250,"callback":224,"file":189,"line":251},"gvn_schart_2_cached",586,[],3,{"dangerousFunctions":255,"sqlUsage":256,"outputEscaping":258,"fileOperations":91,"externalRequests":91,"nonceChecks":28,"capabilityChecks":29,"bundledLibraries":267},[],{"prepared":28,"raw":91,"locations":257},[],{"escaped":259,"rawEcho":28,"locations":260},119,[261,265],{"file":262,"line":263,"context":264},"admin_metabox.php",309,"raw output",{"file":189,"line":266,"context":264},56,[],[269,287],{"entryPoint":270,"graph":271,"unsanitizedCount":91,"severity":286},"gvn_chart_top_form (functions.php:409)",{"nodes":272,"edges":284},[273,278],{"id":274,"type":275,"label":276,"file":189,"line":277},"n0","source","$_GET",418,{"id":279,"type":280,"label":281,"file":189,"line":282,"wp_function":283},"n1","sink","echo() [XSS]",463,"echo",[285],{"from":274,"to":279,"sanitized":241},"low",{"entryPoint":288,"graph":289,"unsanitizedCount":91,"severity":286},"\u003Cfunctions> (functions.php:0)",{"nodes":290,"edges":293},[291,292],{"id":274,"type":275,"label":276,"file":189,"line":277},{"id":279,"type":280,"label":281,"file":189,"line":282,"wp_function":283},[294],{"from":274,"to":279,"sanitized":241},{"summary":296,"deductions":297},"The \"sql-chart-builder\" plugin v2.3.7.2 exhibits a generally strong security posture based on static analysis, with no identified dangerous functions, all SQL queries using prepared statements, and a high percentage of properly escaped output. The limited attack surface and robust use of nonces and capability checks are also positive indicators. However, the presence of two known CVEs, with one remaining unpatched, significantly elevates the risk. The historical vulnerability types (XSS and SQL Injection) suggest that input sanitization and output escaping may have been inconsistently applied in past versions, even though current static analysis indicates improvements. This historical pattern, coupled with an unpatched medium-severity vulnerability, warrants careful attention. While the current code appears to follow many best practices, the outstanding vulnerability is a critical concern that undermines the overall security of the plugin.",[298,301,304],{"reason":299,"points":300},"Unpatched CVEs",15,{"reason":302,"points":303},"Known SQL Injection vulnerabilities",8,{"reason":305,"points":303},"Known Cross-site Scripting vulnerabilities","2026-03-16T19:29:58.295Z",{"wat":308,"direct":314},{"assetPaths":309,"generatorPatterns":311,"scriptPaths":312,"versionParams":313},[310],"\u002Fwp-content\u002Fplugins\u002Fsql-chart-builder\u002Fasset\u002Fimg\u002Frecommended1.jpg",[],[],[],{"cssClasses":315,"htmlComments":320,"htmlAttributes":321,"restEndpoints":323,"jsGlobals":324,"shortcodeOutput":325},[316,317,318,319],"gf-alert","gf-alert-info","gf-alert-danger","guaven-sqlcharts-notice",[],[322],"data-notice=\"onboarding_notice\"",[],[],[]]