[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f7uVfpYjIEYquF07tzM6iEcbkjDF7o0KyfTaABGxDVHk":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":11,"num_ratings":11,"last_updated":13,"tested_up_to":14,"requires_at_least":15,"requires_php":16,"tags":17,"homepage":23,"download_link":24,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27,"vulnerabilities":28,"developer":29,"crawl_stats":26,"alternatives":36,"analysis":136,"fingerprints":168},"page-navigation-by-menu","Page navigation by menu","1.1.1","Lovro Hrust","https:\u002F\u002Fprofiles.wordpress.org\u002Flovor\u002F","\u003Cp>Plugin to support navigation by pages – similar to built in function the_posts_navigation() for posts.\u003Cbr \u002F>\nPages in navigation are filtered by provided menu (Primary menu by default) and sorted in the same order as in menu.\u003Cbr \u002F>\nBy default, main menu is used, but different menu could be used by calling function for displaying with different menu as parameter.\u003C\u002Fp>\n\u003Ch3>Disclaimer!\u003C\u002Fh3>\n\u003Cp>This plugin works only with classic themes. With FSE themes it will not work, since it depends on classic menus.\u003C\u002Fp>\n\u003Ch3>Usage\u003C\u002Fh3>\n\u003Ch4>Basic\u003C\u002Fh4>\n\u003Cp>Just install and call \u003Ccode>the_pages_navigation()\u003C\u002Fcode> in your php template. There is also a \u003Ccode>get_the_pages_navigation()\u003C\u002Fcode> function which returns string with same content.\u003Cbr \u002F>\nArguments to these functions could be supplied, all optional.\u003Cbr \u002F>\n* $menu – a menu ID, slug, name, or object (WP_Term) for which to show pages\u003Cbr \u002F>\n* $start_position – start position from which position in menu to start navigation\u003Cbr \u002F>\n? $end_position – to which position in menu to show navigation\u003C\u002Fp>\n\u003Ch4>Advanced\u003C\u002Fh4>\n\u003Cp>There are filters that can help to customize plugin output.\u003C\u002Fp>\n\u003Cp>Change menu filter\u003C\u002Fp>\n\u003Cpre>\u003Ccode>apply_filters('page_nav_menu', $default_menu)\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Filters menu used for navigation.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>$default_menu – a menu ID, slug, name, or object (WP_Term)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Arrow filters\u003C\u002Fp>\n\u003Cpre>\u003Ccode>apply_filters( 'page_nav_left_arrow', $HTML )\napply_filters( 'page_nav_right_arrow', $HTML )\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Filters arrow output.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>$HTML – HTML of arrow, coded as SVG, img or something else.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Filter output\u003C\u002Fp>\n\u003Cpre>\u003Ccode>apply_filters( 'arrow_wrapper', $HTML_output, $left, $enabled, $output_image, $output_link, $output_div, $output_text )\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Filters whole HTML output.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>$HTML_output – as the name says\u003C\u002Fli>\n\u003Cli>$left – output is for left side (previous)\u003C\u002Fli>\n\u003Cli>$enabled – navigation on that side is enabled\u003C\u002Fli>\n\u003Cli>$output_image – html of arrow image\u003C\u002Fli>\n\u003Cli>$output_link – URL of link to which arrow leads\u003C\u002Fli>\n\u003Cli>$output_div – wrapper of text besides arrow\u003C\u002Fli>\n\u003Cli>$output_text – text besides arrow\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Examples of filtering\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>add_filter( 'page_nav_left_arrow', function() {\n    return '\u003Csvg width=\"53\" height=\"32\" viewBox=\"0 0 53 32\" fill=\"none\" xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\">\u003Cpath d=\"M51.77 15.994H1M16.622 31L1 15.998 16.622 1v30z\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"\u002F>\u003C\u002Fsvg>';\n} );\n\u003C\u002Fcode>\u003C\u002Fpre>\n","Create navigation to next\u002Fprevious pages similar to navigation for posts. Previous and next pages are determined from menu.",0,1373,"2025-12-05T00:31:00.000Z","6.9.4","4.9","5.6",[18,19,20,21,22],"menu","navigation","next","page","previous","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fpage-navigation-by-menu.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":25,"avg_patch_time_days":33,"trust_score":34,"computed_at":35},"lovor",4,3000,30,94,"2026-04-04T13:51:58.028Z",[37,58,76,97,117],{"slug":38,"name":39,"version":40,"author":41,"author_profile":42,"description":43,"short_description":44,"active_installs":45,"downloaded":46,"rating":47,"num_ratings":48,"last_updated":49,"tested_up_to":50,"requires_at_least":51,"requires_php":23,"tags":52,"homepage":55,"download_link":56,"security_score":57,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"exclude-pages","Exclude Pages","1.92","Simon Wheatley","https:\u002F\u002Fprofiles.wordpress.org\u002Fsimonwheatley\u002F","\u003Cp>This plugin adds a checkbox, “include this page in menus”, uncheck this to exclude pages from the page navigation that users see on your site.\u003C\u002Fp>\n\u003Cp>Any issues: \u003Ca href=\"http:\u002F\u002Fwww.simonwheatley.co.uk\u002Fcontact-me\u002F\" rel=\"nofollow ugc\">contact me\u003C\u002Fa>.This plugin adds a checkbox, “include this page in menus”, which is checked by default. If you uncheck\u003Cbr \u002F>\nit, the page will not appear in any listings of pages (which includes, and is \u003Cem>usually\u003C\u002Fem> limited to, your\u003Cbr \u002F>\npage navigation menus).\u003C\u002Fp>\n\u003Cp>Pages which are children of excluded pages also do not show up in menu listings. (An alert in the editing screen,\u003Cbr \u002F>\nunderneath the “include” checkbox allows you to track down which ancestor page is affecting child pages\u003Cbr \u002F>\nin this way.)\u003C\u002Fp>\n\u003Ch3>Advanced Usage\u003C\u002Fh3>\n\u003Cp>It is possible to temporarily pause and resume the effect of Exclude Pages by using the new \u003Ccode>\u003C?php pause_exclude_pages(); ?>\u003C\u002Fcode> and \u003Ccode>\u003C?php resume_exclude_pages(); ?>\u003C\u002Fcode> templates tags. The following code will show a list of all pages in your site, even those normally hidden:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003C?php pause_exclude_pages(); ?>\n\u003C?php wp_list_pages('title_li=\u003Ch2>Pages\u003C\u002Fh2>' ); ?>\n\u003C?php resume_exclude_pages(); ?>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>You can also get an array the IDs of the pages which are excluded by calling the function \u003Ccode>ep_get_excluded_ids();\u003C\u002Fcode>, you can then use these IDs as you wish (e.g. feed them into raw MySQL queries).\u003C\u002Fp>\n\u003Cp>Note to other plugin authors:\u003C\u002Fp>\n\u003Cp>The plugin does not operate on wp_list_pages while the user is on an admin page, if this is an issue you can take advantage of the \u003Ccode>ep_admin_bail_out\u003C\u002Fcode> filter and create a filter function which returns false to allow Exclude Pages to operate in the admin area.\u003C\u002Fp>\n\u003Cp>Another note:\u003C\u002Fp>\n\u003Cp>If your plugins or themes don’t use the standard WordPress functions to create their menus then they won’t work. To get them to work you will need to track down the bit of code in the theme\u002Fplugin which gets the pages and change it to apply the filter “get_pages” (I cannot be responsible for any unforseen effects of the changes you make, so please test thoroughly). The change to getting pages will probably look something like this:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$pages = apply_filters( 'get_pages', $pages );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Please \u003Ca href=\"http:\u002F\u002Fwww.simonwheatley.co.uk\u002Fcontact-me\u002F\" rel=\"nofollow ugc\">contact me\u003C\u002Fa> if you’re completely stuck and we can discuss possible solutions.\u003C\u002Fp>\n\u003Cp>Exclude pages is incompatible with:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fwordpress-css-drop-down-menu\u002F\" rel=\"ugc\">WP CSS Dropdown Menus\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fthemes\u002Fphantom\" rel=\"ugc\">Phantom theme\u003C\u002Fa> – This theme\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Requests & Bug Reports\u003C\u002Fh3>\n\u003Cp>I’m simply noting requests & bug reports here, I’ve not necessarily looked into any of these.\u003C\u002Fp>\n\u003Cp>\u003Cem>None!\u003C\u002Fem>\u003C\u002Fp>\n","This plugin adds a checkbox, “include this page in menus”, uncheck this to exclude pages from the page navigation that users see on your site.",30000,1037162,98,47,"2017-11-28T03:16:00.000Z","3.4.2","2.2.3",[38,53,54,18,19],"get_pages","hide-pages","http:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fexclude-pages\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fexclude-pages.1.92.zip",85,{"slug":59,"name":60,"version":61,"author":62,"author_profile":63,"description":64,"short_description":65,"active_installs":66,"downloaded":67,"rating":68,"num_ratings":69,"last_updated":70,"tested_up_to":71,"requires_at_least":61,"requires_php":23,"tags":72,"homepage":74,"download_link":75,"security_score":57,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"exclude-pages-from-menu","Exclude Pages From Menu","3.0","Vinod Dalvi","https:\u002F\u002Fprofiles.wordpress.org\u002Fvinod-dalvi\u002F","\u003Cp>Exclude Pages From Menu plugin provides easy option to remove any page from navigation menu.\u003C\u002Fp>\n\u003Cp>The plugin provides option in the page edit screen in admin area which you can use to remove the page from menu display in the site front end.\u003C\u002Fp>\n\u003C\u002Fp>\n\u003Cp>Like Exclude Pages From Menu? \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fexclude-pages-from-menu\u002Freviews\u002F?filter=5#new-post\" rel=\"ugc\">Give us a rating\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>Need Help or Have Suggestions? contact us on \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fexclude-pages-from-menu\u002F\" rel=\"ugc\">Plugin support forum\u003C\u002Fa>\u003C\u002Fp>\n","The plugin provides option in the page edit screen to remove page from navigation menu in the front end of site.",9000,111447,70,19,"2021-03-14T14:40:00.000Z","5.7.15",[38,59,54,18,73],"remove-pages-from-navigation","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fexclude-pages-from-menu\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fexclude-pages-from-menu.3.0.zip",{"slug":77,"name":78,"version":79,"author":80,"author_profile":81,"description":82,"short_description":83,"active_installs":84,"downloaded":85,"rating":86,"num_ratings":87,"last_updated":88,"tested_up_to":14,"requires_at_least":89,"requires_php":90,"tags":91,"homepage":95,"download_link":96,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"auto-submenu","Auto Submenu","1.0.5","Diana van de Laarschot","https:\u002F\u002Fprofiles.wordpress.org\u002Fanaid\u002F","\u003Cp>The default custom menu in WordPress only allows checking the “Automatically add new top-level pages” (Appearance > Menus) or adding a Navigation block with all pages and all child pages (Appearance > Editor).\u003C\u002Fp>\n\u003Cp>With Auto Submenu you get extra functionality to automatically include child pages into the menu.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>NEW: ASM now provides support for the Customizer via Appearance > Customize\u003C\u002Fstrong>\u003Cbr \u002F>\n\u003Cstrong>NEW: ASM now provides support for Full Site Editing with the Gutenberg Block Editor via Appearance > Editor\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch3>Using it\u003C\u002Fh3>\n\u003Cp>Enable the plugin and go to Appearance > Editor.\u003C\u002Fp>\n\u003Cp>For each Page in your menu, you now have the following extra configuration options:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Add child pages as submenu y\u002Fn; \u003C\u002Fli>\n\u003Cli>child pages are ordered ascending by Menu Order;\u003C\u002Fli>\n\u003Cli>specify the (maximum) nesting depth of children you want to show (max 3);\u003C\u002Fli>\n\u003Cli>specify the title for the child pages. For this you can use %post_title, %post_author and other wildcards, see ‘Other Notes > Wildcards’. Default value: %post_title\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Via Appearance > Menus and Appearance > Customize you also get the following option:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Check the “Automatically add new top-level and all its child pages to this menu (Auto Submenu)”-checkbox.\u003C\u002Fli>\n\u003Cli>If this option is checked, all top-level pages will automatically be added and will automatically have all child pages added as submenu.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>With the Free version you cannot control the nesting depth of the child pages, all subpages are added, regardless the depth of the page tree.\u003C\u002Fp>\n\u003Ch4>Wildcards\u003C\u002Fh4>\n\u003Cp>You can control the title of the menu items generated by the plug-in with the following wildcards:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>%post_title\u003C\u002Fli>\n\u003Cli>%post_author\u003C\u002Fli>\n\u003Cli>%post_date for the unformatted post date: 2012-11-10 18:14:23\u003C\u002Fli>\n\u003Cli>%post_date() for a formatted post date with the following default formatting: November 10th, 2012\u003C\u002Fli>\n\u003Cli>%post_date(\u003Cyour formatting here>) for custom date formatting. Example: %post_date(l jS \\of F Y, h:i:s A). See \u003Ca href=\"https:\u002F\u002Fcodex.wordpress.org\u002FFormatting_Date_and_Time\" rel=\"nofollow ugc\">https:\u002F\u002Fcodex.wordpress.org\u002FFormatting_Date_and_Time\u003C\u002Fa> for formatting options.\u003C\u002Fli>\n\u003Cli>%post_date_gmt\u003C\u002Fli>\n\u003Cli>%post_date_gmt()\u003C\u002Fli>\n\u003Cli>%post_date_gmt(\u003Cyour formatting here>)\u003C\u002Fli>\n\u003C\u002Ful>\n","Dynamic menus: Add a page to your menu and then let WordPress automatically add the child pages.",2000,51638,80,25,"2025-12-03T15:55:00.000Z","5.4","7.4",[18,19,92,93,94],"pages","submenu","subpages","https:\u002F\u002Fwordpress.telodelic.nl\u002Fauto-submenu","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fauto-submenu.1.0.5.zip",{"slug":98,"name":99,"version":100,"author":101,"author_profile":102,"description":103,"short_description":104,"active_installs":84,"downloaded":105,"rating":106,"num_ratings":107,"last_updated":108,"tested_up_to":109,"requires_at_least":61,"requires_php":23,"tags":110,"homepage":115,"download_link":116,"security_score":57,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"wp-post-navigation","WP Post Navigation","1.2.4","Anas Mir","https:\u002F\u002Fprofiles.wordpress.org\u002Fsharpcoders\u002F","\u003Cp>WP Post Navigation Plugin gives you facility to show Previous and Next Post Links at the Top or Bottom of a Post.\u003Cbr \u002F>\nYou can set to navigate within category or date wise navigation. You’ve the option to set Post Navigation Bar at Bottom, Top or both Top & Bottom.\u003Cbr \u002F>\nYou can apply CSS style to Previous and Next Post Links. You can set custom text instead of Next and Previous Post Titles.\u003Cbr \u002F>\nYou can set custom Image for Next and Previous Post Links.\u003Cbr \u002F>\nManually Place Post Navigation in single.php, just Copy & paste following code anywhere in single.php page under get_header();\u003Cbr \u002F>\n\u003C?php echo isset( $WPPostNavigation ) ? $WPPostNavigation->WP_Custom_Post_Navigation():”; ?>\u003Cbr \u002F>\nFor Help visit: http:\u002F\u002Fsharp-coders.com\u002Fwp-post-navigation\u002F\u003C\u002Fp>\n","Show Next and Previous Post Links at Posts.",57395,82,26,"2017-11-28T18:10:00.000Z","4.7.32",[111,112,113,114,98],"next-and-previous-post","next-post-link","post-navigation","previous-post-link","http:\u002F\u002Fsharp-coders.com\u002Fwp-post-navigation","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-post-navigation.zip",{"slug":118,"name":119,"version":120,"author":121,"author_profile":122,"description":123,"short_description":124,"active_installs":125,"downloaded":126,"rating":106,"num_ratings":127,"last_updated":128,"tested_up_to":129,"requires_at_least":130,"requires_php":131,"tags":132,"homepage":23,"download_link":135,"security_score":57,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"buttons-to-edit-next-previous-post","Buttons to Edit Next\u002FPrevious Post","1.2","Aftab Ali Muni","https:\u002F\u002Fprofiles.wordpress.org\u002Faftabmuni\u002F","\u003Cp>This plugin will add easy shortcut buttons to edit next and previous post in admin edit-post page. You can directly navigate to next and previous post.\u003C\u002Fp>\n","This plugin will add easy shortcut buttons to edit next and previous post in admin edit-post page. You can directly navigate to next and previous post …",1000,11244,11,"2023-11-26T07:23:00.000Z","6.4.8","3.2","5.0",[133,134],"edit-next-previous-post-button-in-admin","edit-post-page-add-new-button","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fbuttons-to-edit-next-previous-post.zip",{"attackSurface":137,"codeSignals":148,"taintFlows":160,"riskAssessment":161,"analyzedAt":167},{"hooks":138,"ajaxHandlers":144,"restRoutes":145,"shortcodes":146,"cronEvents":147,"entryPointCount":11,"unprotectedCount":11},[139],{"type":140,"name":141,"callback":142,"file":143,"line":107},"action","the_post","page_nav_by_menu\\page_nav_initialization_callback","internal.php",[],[],[],[],{"dangerousFunctions":149,"sqlUsage":150,"outputEscaping":152,"fileOperations":11,"externalRequests":11,"nonceChecks":11,"capabilityChecks":11,"bundledLibraries":159},[],{"prepared":11,"raw":11,"locations":151},[],{"escaped":153,"rawEcho":153,"locations":154},1,[155],{"file":156,"line":157,"context":158},"index.php",74,"raw output",[],[],{"summary":162,"deductions":163},"Based on the static analysis, the \"page-navigation-by-menu\" v1.1.1 plugin exhibits a strong security posture with no identified critical vulnerabilities in its code. The absence of AJAX handlers, REST API routes, shortcodes, and cron events significantly limits the potential attack surface. Furthermore, the plugin demonstrates good development practices by utilizing prepared statements for all SQL queries and avoiding file operations or external HTTP requests. The lack of identified dangerous functions and the absence of taint analysis flows with unsanitized paths are also positive indicators.\n\nHowever, there are a few areas that warrant attention. The plugin has a low number of output operations, and only 50% of these are properly escaped. This could potentially lead to cross-site scripting (XSS) vulnerabilities if user-supplied data is not handled carefully in the unescaped outputs. Additionally, the absence of any recorded vulnerabilities in its history is positive, but it's important to note that this doesn't guarantee future immunity. The plugin's limited functionality might contribute to its clean history, but vigilance is always recommended.\n\nIn conclusion, the plugin appears to be relatively secure due to its minimal attack surface and proper handling of critical areas like SQL. The primary concern lies in the incomplete output escaping, which, though affecting a small number of outputs, should be addressed to prevent potential XSS. The lack of any historical vulnerabilities is a strength, suggesting a well-maintained codebase, but the plugin's overall feature set is also limited, which might be a contributing factor.",[164],{"reason":165,"points":166},"Unescaped output present",5,"2026-03-17T06:23:48.917Z",{"wat":169,"direct":176},{"assetPaths":170,"generatorPatterns":172,"scriptPaths":173,"versionParams":174},[171],"\u002Fwp-content\u002Fplugins\u002Fpage-navigation-by-menu\u002Fpage-navigation-by-menu.php",[],[],[175],"page-navigation-by-menu\u002Fpage-navigation-by-menu.php?ver=1.1.1",{"cssClasses":177,"htmlComments":179,"htmlAttributes":180,"restEndpoints":181,"jsGlobals":182,"shortcodeOutput":183},[178],"page-navigation",[],[],[],[],[]]