[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fIhiMvaG3pXP9mKjYYnsQyVDkc-rcA3t8BP7VJ5Ni_Sw":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":13,"last_updated":14,"tested_up_to":15,"requires_at_least":16,"requires_php":17,"tags":18,"homepage":24,"download_link":25,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28,"vulnerabilities":29,"developer":30,"crawl_stats":27,"alternatives":35,"analysis":121,"fingerprints":180},"ct-page-editors","CT Page Editors","0.0.1","cntran","https:\u002F\u002Fprofiles.wordpress.org\u002Fcntran\u002F","\u003Cp>Easiest and mostly configureless way to add additional WP wysiswg editors to any custom page template.\u003C\u002Fp>\n","CT Page Editors allows you to add extra editable sections onto any custom page template.",10,1956,0,"2015-04-13T16:30:00.000Z","4.1.42","3.0.1","",[19,20,21,22,23],"admin","cms","formatting","page","pages","https:\u002F\u002Fwww.facebook.com\u002Fctpageeditors","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fct-page-editors.zip",85,null,"2026-03-15T15:16:48.613Z",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":31,"total_installs":11,"avg_security_score":26,"avg_patch_time_days":32,"trust_score":33,"computed_at":34},1,30,84,"2026-04-04T14:43:08.027Z",[36,53,71,86,104],{"slug":37,"name":38,"version":39,"author":40,"author_profile":41,"description":42,"short_description":43,"active_installs":44,"downloaded":45,"rating":33,"num_ratings":46,"last_updated":47,"tested_up_to":48,"requires_at_least":49,"requires_php":17,"tags":50,"homepage":51,"download_link":52,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"pagely-multiedit","Pagely MultiEdit","0.9.8.6","joshua strebel","https:\u002F\u002Fprofiles.wordpress.org\u002Fjoshuastrebel\u002F","\u003Cp>One thing I always wished WP would do better is allow for multiple editable content blocks on page templates. This plugin uses custom fields to create simple tinyMCE editable regions on page templates.\u003C\u002Fp>\n\u003Cp>See Instructions and Usage Examples here: \u003Ca href=\"https:\u002F\u002Fpagely.com\u002Fmultiedit-plugin\u002F\" rel=\"nofollow ugc\">Pagely MultiEdit plugin\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>NOTE: Must be used inside\u002Fafter the opening loop statement:\u003Cbr \u002F>\nwhile (have_posts()) : the_post();\u003Cbr \u002F>\n  multieditDisplay(‘YourBlockName’);\u003C\u002Fp>\n\u003Cp>Brought to you by: \u003Ca href=\"https:\u002F\u002Fpagely.com\" rel=\"nofollow ugc\">Pagely WordPress Hosting\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>Follow \u003Ca href=\"http:\u002F\u002Ftwitter.com\u002Fstrebel\" rel=\"nofollow ugc\">@strebel\u003C\u002Fa> and feel free to check out \u003Ca href=\"https:\u002F\u002Fpagely.com\" rel=\"nofollow ugc\">Pagely\u003C\u002Fa>\u003C\u002Fp>\n","MultiEdit adds tinyMCE editable \"blocks\" to WordPress custom page templates.",300,34377,5,"2016-05-10T20:26:00.000Z","4.5.33","2.9",[19,20,21,22,23],"https:\u002F\u002Fpagely.com\u002Fmultiedit-plugin\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fpagely-multiedit.zip",{"slug":54,"name":55,"version":56,"author":57,"author_profile":58,"description":59,"short_description":60,"active_installs":44,"downloaded":61,"rating":62,"num_ratings":31,"last_updated":63,"tested_up_to":64,"requires_at_least":65,"requires_php":17,"tags":66,"homepage":69,"download_link":70,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"content-management-system-dashboard","CMS Dashboard","2.0","3pointross","https:\u002F\u002Fprofiles.wordpress.org\u002F3pointross\u002F","\u003Cp>Improve the usability of your WordPress CMS system. This plug-in creates a dashboard widget with clearly labeled large buttons of the most common tasks one would perform when using wordpress as a content management system.\u003C\u002Fp>\n\u003Cp>I have found that particularly when handing a WordPress CMS over to less than tech-savvy clients, there is often confusion on how to perform some of the more simple tasks simply because the WordPress side menu can be overwhelming. This plugin creates a simple to use dashboard interface that will let clients easily post, edit, manage users and change widgets with out having to do any hunting or searching.\u003C\u002Fp>\n","Improve the usability of your Wordpress CMS system. This plug-in creates a dashboard widget with clearly labeled large buttons of the most common task …",23105,80,"2010-09-07T19:39:00.000Z","3.0.5","3.0",[19,67,68,20,23],"administration","client","http:\u002F\u002Fworkshop.37designs.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcontent-management-system-dashboard.zip",{"slug":72,"name":73,"version":74,"author":75,"author_profile":76,"description":77,"short_description":78,"active_installs":44,"downloaded":79,"rating":62,"num_ratings":80,"last_updated":81,"tested_up_to":82,"requires_at_least":65,"requires_php":17,"tags":83,"homepage":84,"download_link":85,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"lock-pages","Lock Pages","0.3.1","Steve Taylor","https:\u002F\u002Fprofiles.wordpress.org\u002Fgyrus\u002F","\u003Cp>NOTE: This plugin is not tested with Gutenberg, and we have no near-term plans to do so. If using WP > 5.0, use the Classic Editor if there are problems.\u003C\u002Fp>\n\u003Cp>NOTE: This plugin was originally designed to only lock pages, and only later added custom post type functionality. Hence the name, and sometimes the terminology will say “pages” when it means “any post type”.\u003C\u002Fp>\n\u003Cp>Sometimes some pages or other posts are too important to allow them to be casually moved about or deleted by site editors. An editor may think nothing of renaming a page’s slug, or deleting a page to replace it with something similar, perhaps unaware of effects on SEO. Also, certain pages might be essential to keep in place because of a site’s structure, or because of aspects of a custom theme.\u003C\u002Fp>\n\u003Cp>This plugin lets administrators “lock” any or all pages, and any post of any post type. “Locking” here basically means preventing non-admins from:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Editing the item’s slug\u003C\u002Fli>\n\u003Cli>Changing the item’s parent\u003C\u002Fli>\n\u003Cli>Changing the item’s template\u003C\u002Fli>\n\u003Cli>Deleting the item\u003C\u002Fli>\n\u003Cli>Changing the item’s status\u003C\u002Fli>\n\u003Cli>Changing the item’s password protection\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Locking is implemented by preventing the actual database update being performed as well as, where possible, having the interface element for that field removed. Where possible interface elements are removed via WP filters on the server; otherwise, jQuery is used on the client.\u003C\u002Fp>\n\u003Cp>NOTE: Currently, I’ve been unable to get this working with the Quick Edit functionality. As a stop-gap measure, which is only in place because it seems to be better than nothing, the Quick Edit link is removed for users who can’t edit locked pages. I know, it’s not great. But until I work out how to selectively block Quick Editing, I’m assuming a locked page should be locked. Users can always edit the other fields via the normal edit page.\u003C\u002Fp>\n\u003Cp>Go to GitHub for \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fgyrus\u002FLock-Pages\" rel=\"nofollow ugc\">development code\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fgyrus\u002FLock-Pages\u002Fissues\" rel=\"nofollow ugc\">issue tracking\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Known issues\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Quick Edit presents problems. I’ve worked out how to create hidden fields in the Quick Edit box, and to put the values in the hidden div, but I can’t work out how to dynamically populate the fields with the values, so the old values can be used if necessary on saving. For now Quick Edit is blocked for users who can’t edit locked pages.\u003C\u002Fli>\n\u003Cli>Although I’ve fixed the lock_parent function so it allows uploaded files to be attached to a locked page, it still prevents media already in the library from being attached when inserted.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Ideas\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Include the locking checkbox for admins in the Quick Edit form.\u003C\u002Fli>\n\u003Cli>On the settings screen, use a drop-down for selecting which capability is needed for editing locked page elements.\u003C\u002Fli>\n\u003Cli>Implement a system to deal with descendants, e.g. an option to lock all descendants of a locked page or not.\u003C\u002Fli>\n\u003C\u002Ful>\n","Lock Pages prevents specified pages (or all pages), posts, or custom post types from having their slug, parent, status or password edited, or from bei …",17843,2,"2018-12-19T15:28:00.000Z","4.9.29",[19,67,20,22,23],"http:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Flock-pages\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Flock-pages.0.3.1.zip",{"slug":87,"name":88,"version":89,"author":90,"author_profile":91,"description":92,"short_description":93,"active_installs":94,"downloaded":95,"rating":13,"num_ratings":13,"last_updated":96,"tested_up_to":97,"requires_at_least":98,"requires_php":17,"tags":99,"homepage":102,"download_link":103,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"category-page-extender","Category Page Extender","1.0.3","grpsmglr00","https:\u002F\u002Fprofiles.wordpress.org\u002Fgrpsmglr00\u002F","\u003Cp>This plugin builds on the Category Page plugin making it possible to automatically insert posts into pages and subpages based on categories.  You must have a current version of \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fpage2cat\u002F\" rel=\"ugc\">Category Page\u003C\u002Fa> installed in order to function.\u003Cbr \u002F>\n.\u003Cbr \u002F>\nVisit plugin page \u003Ca href=\"http:\u002F\u002Fcategorypageextender.wordpress.com\u002F\" rel=\"nofollow ugc\">here\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch3>Usage\u003C\u002Fh3>\n\u003Cp>To view complete instructions \u003Ca href=\"http:\u002F\u002Fcategorypageextender.wordpress.com\" rel=\"nofollow ugc\">read here\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>Open up page.php in your template folder (you may also set up a seperate a Page Template)\u003C\u002Fp>\n\u003Cp>For the most basic setup, insert the following below the loop statement in the page.php file:\u003C\u002Fp>\n\u003Cpre>\u003C?php if( function_exists(page2cat_pages)){ page2cat_pages($post->ID);} ?>\u003C\u002Fpre>\n\u003C\u002Fp>\n\u003Cp>I recommend you wrap the function in your standard post class.  For example:\u003C\u002Fp>\n\u003Cpre>\u003Cdiv class=\"post\">\n\u003C?php if( function_exists(page2cat_pages)){ page2cat_pages($post->ID);} ?>\n\u003C\u002Fdiv>\u003C\u002Fpre>\n\u003C\u002Fp>\n\u003Cp>Plugin Options\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003C?php if( function_exists(page2cat_pages)){ page2cat_pages($post->ID, posts per page, number of pages);} ?>\u003Cbr \u002F>\u003Cbr \u002F>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Posts per page: (default = 10) set to 0 to show all\u003Cbr \u002F>\nThis sets the number of posts to show at one time on the page.\u003C\u002Fp>\n\u003Cp>Number of pages: (default = 15) set to 0 to show all\u003Cbr \u002F>\nThis tells how many page numbers to show at a time on the page navigation bar.\u003C\u002Fp>\n\u003Cp>Example of Category Page Extender with variables:\u003C\u002Fp>\n\u003Cpre>\u003C?php if( function_exists(page2cat_pages)){ page2cat_pages($post->ID, 5, 10);} ?>\u003C\u002Fpre>\n\u003Cp>This will list 5 posts and up to 10 page numbers at a time on the page navigation bar.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"http:\u002F\u002Fcategorypageextender.wordpress.com\u002F\" rel=\"nofollow ugc\">Plugin Homepage\u003C\u002Fa>\u003C\u002Fp>\n","Inserts posts into pages corresponding to category.  Add on plugin for Category Page by pixline.net. Requieres an active installation of Category Page …",40,10621,"2009-12-31T13:44:00.000Z","2.8.4","2.2",[19,100,101,21,23],"categories","category","http:\u002F\u002Fcategorypageextender.wordpress.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcategory-page-extender.1.0.3.zip",{"slug":105,"name":106,"version":107,"author":108,"author_profile":109,"description":110,"short_description":111,"active_installs":112,"downloaded":113,"rating":13,"num_ratings":13,"last_updated":114,"tested_up_to":97,"requires_at_least":115,"requires_php":17,"tags":116,"homepage":119,"download_link":120,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"wp-cms","WP-CMS","2.1","Gilbert Pellegrom","https:\u002F\u002Fprofiles.wordpress.org\u002Fgilbitron\u002F","\u003Cp>WP-CMS is a plugin for WordPress that changes the functionality of the WordPress admin backend to act more like a CMS.\u003Cbr \u002F>\nThe blog functionality becomes optional and the focus is on writing pages to make WordPress as user friendly for\u003Cbr \u002F>\nyou and your clients as possible.\u003C\u002Fp>\n","WP-CMS is a plugin for Wordpress that changes the functionality of the Wordpress admin backend to act more like a CMS.",20,19118,"2009-08-17T15:19:00.000Z","2.7",[19,117,20,118,23],"blog","content","http:\u002F\u002Fwww.gilbertpellegrom.co.uk\u002Fprojects\u002Fwp-cms\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-cms.2.1.zip",{"attackSurface":122,"codeSignals":138,"taintFlows":150,"riskAssessment":169,"analyzedAt":179},{"hooks":123,"ajaxHandlers":134,"restRoutes":135,"shortcodes":136,"cronEvents":137,"entryPointCount":13,"unprotectedCount":13},[124,130],{"type":125,"name":126,"callback":127,"file":128,"line":129},"action","admin_init","ctpe_admin_init","ct-page-editors.php",13,{"type":125,"name":131,"callback":132,"file":128,"line":133},"save_post","ctpe_save_post",14,[],[],[],[],{"dangerousFunctions":139,"sqlUsage":140,"outputEscaping":142,"fileOperations":13,"externalRequests":13,"nonceChecks":13,"capabilityChecks":13,"bundledLibraries":149},[],{"prepared":13,"raw":13,"locations":141},[],{"escaped":31,"rawEcho":80,"locations":143},[144,147],{"file":128,"line":145,"context":146},136,"raw output",{"file":128,"line":148,"context":146},141,[],[151],{"entryPoint":152,"graph":153,"unsanitizedCount":13,"severity":168},"\u003Cct-page-editors> (ct-page-editors.php:0)",{"nodes":154,"edges":165},[155,160],{"id":156,"type":157,"label":158,"file":128,"line":159},"n0","source","$_POST",105,{"id":161,"type":162,"label":163,"file":128,"line":145,"wp_function":164},"n1","sink","echo() [XSS]","echo",[166],{"from":156,"to":161,"sanitized":167},true,"low",{"summary":170,"deductions":171},"Based on the provided static analysis and vulnerability history, the \"ct-page-editors\" plugin v0.0.1 exhibits a generally positive security posture. The absence of any discovered CVEs and the fact that none are currently unpatched strongly suggest a history of good security practices or a lack of prior detailed security scrutiny. The code analysis reveals a commendable lack of direct SQL injection risks due to the exclusive use of prepared statements and a clean slate regarding file operations and external HTTP requests. Furthermore, the zero-risk taint analysis indicates no critical or high-severity vulnerabilities related to data flow within the analyzed code. However, a significant concern arises from the complete lack of any nonces, capability checks, or proper output escaping, leaving it susceptible to potential cross-site scripting (XSS) and cross-site request forgery (CSRF) attacks, especially if any entry points were to be introduced in future versions. The attack surface, while currently zero, offers no inherent protection mechanisms.\n\nWhile the current state shows no immediate critical threats, the absence of fundamental security checks like nonce and capability checks is a considerable weakness. The 33% proper output escaping also indicates potential for XSS vulnerabilities if the unescaped outputs are ever exposed to user-controlled data. This indicates that while the plugin may not have been targeted or exploited in the past, it lacks robust defenses that are standard for secure WordPress development. Future development must prioritize implementing appropriate nonce and capability checks for any new entry points and ensure all output is properly escaped to mitigate these identified risks.",[172,175,177],{"reason":173,"points":174},"Missing nonce checks",8,{"reason":176,"points":174},"Missing capability checks",{"reason":178,"points":46},"Only 33% of outputs properly escaped","2026-03-17T00:23:46.341Z",{"wat":181,"direct":186},{"assetPaths":182,"generatorPatterns":183,"scriptPaths":184,"versionParams":185},[],[],[],[],{"cssClasses":187,"htmlComments":188,"htmlAttributes":189,"restEndpoints":190,"jsGlobals":191,"shortcodeOutput":192},[],[],[],[],[],[193],"ctpe_content"]