[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fYyvxaFUCkvzp7IWFT8_ACqq6CXByJV607qdSG6f8IKs":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":19,"download_link":20,"security_score":21,"vuln_count":13,"unpatched_count":13,"last_vuln_date":22,"fetched_at":23,"vulnerabilities":24,"developer":25,"crawl_stats":22,"alternatives":32,"analysis":33,"fingerprints":70},"remember-my-template","Remember My Template","0.1","Stephen Harris","https:\u002F\u002Fprofiles.wordpress.org\u002Fstephenharris\u002F","\u003Cp>\u003Cstrong>This plug-in requires 3.4+\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>WordPress only stores the page template for the theme which was activated when the page was last saved. Effectively, if you switch back and forth between themes WordPress forgets which template it is suppose to use for any particular page. This is problematic if you are showcasing a plug-in and wish to allow the end user to switch between a selection of thems (via \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Ftheme-switcher\u002F\" rel=\"ugc\">Theme Switcher\u003C\u002Fa>, for example), and don’t want the page templates being reset to ‘default’.\u003C\u002Fp>\n\u003Cp>This plug-in resolves that problem. Whenever you save a page, the plug-in stores the theme-template pair. If you switch themes and save the page, it also stores that theme-template pair too. On switching between the two themes the appropriate template is ‘remembered’.\u003C\u002Fp>\n\u003Cp>Obviously for the plug-in to work you’ll need to save the appropriate template for the page for each theme you’ll be switching between. Currently, this includes the \u003Cem>current theme\u003C\u002Fem>.\u003C\u002Fp>\n\u003Cp>This plug-in doesn’t add any settings – it just works silently in the background, doing its thing.\u003C\u002Fp>\n","Remembers the template that was selected when the theme was last used",10,1669,0,"2013-07-04T22:24:00.000Z","3.5.2","3.4","",[],"http:\u002F\u002Fwww.stephenharris.info","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fremember-my-template.0.1.zip",85,null,"2026-03-15T15:16:48.613Z",[],{"slug":26,"display_name":7,"profile_url":8,"plugin_count":27,"total_installs":28,"avg_security_score":21,"avg_patch_time_days":29,"trust_score":30,"computed_at":31},"stephenharris",6,22740,30,84,"2026-04-04T15:58:06.538Z",[],{"attackSurface":34,"codeSignals":54,"taintFlows":61,"riskAssessment":62,"analyzedAt":69},{"hooks":35,"ajaxHandlers":50,"restRoutes":51,"shortcodes":52,"cronEvents":53,"entryPointCount":13,"unprotectedCount":13},[36,42,45],{"type":37,"name":38,"callback":39,"priority":11,"file":40,"line":41},"action","updated_post_meta","rmt_update_post_template_meta","remember-my-template.php",37,{"type":37,"name":43,"callback":39,"priority":11,"file":40,"line":44},"added_post_meta",38,{"type":46,"name":47,"callback":48,"priority":11,"file":40,"line":49},"filter","get_post_metadata","rmt_get_post_template_meta",70,[],[],[],[],{"dangerousFunctions":55,"sqlUsage":56,"outputEscaping":58,"fileOperations":13,"externalRequests":13,"nonceChecks":13,"capabilityChecks":13,"bundledLibraries":60},[],{"prepared":13,"raw":13,"locations":57},[],{"escaped":13,"rawEcho":13,"locations":59},[],[],[],{"summary":63,"deductions":64},"The \"remember-my-template\" v0.1 plugin exhibits a strong security posture based on the provided static analysis.  The absence of any identified attack surface, dangerous functions, unsanitized taint flows, or external HTTP requests is highly commendable.  Furthermore, the plugin demonstrates excellent coding practices by utilizing prepared statements for all SQL queries and properly escaping all outputs, indicating a proactive approach to preventing common vulnerabilities like SQL injection and XSS.\n\nThe vulnerability history is also a significant positive. With zero known CVEs, it suggests a history of stable and secure development. This lack of historical issues, combined with the clean static analysis, points towards a plugin that is likely well-maintained and resistant to known exploits.  The plugin's strengths lie in its minimal attack surface and diligent use of secure coding practices.\n\nHowever, the most notable concern arises from the complete absence of any nonce checks or capability checks. While the current analysis shows no direct entry points that would immediately exploit this, it represents a significant potential weakness.  A plugin that relies solely on the absence of immediate exploit vectors without implementing fundamental security mechanisms like nonce and capability checks is vulnerable to being exploited if any new entry points are introduced in future updates or if attackers find indirect ways to trigger its functionality without meeting standard WordPress authorization requirements. This oversight, despite the otherwise clean code, represents the primary risk.",[65,67],{"reason":66,"points":11},"Missing nonce checks",{"reason":68,"points":11},"Missing capability checks","2026-03-17T00:22:30.458Z",{"wat":71,"direct":76},{"assetPaths":72,"generatorPatterns":73,"scriptPaths":74,"versionParams":75},[],[],[],[],{"cssClasses":77,"htmlComments":78,"htmlAttributes":79,"restEndpoints":80,"jsGlobals":81,"shortcodeOutput":82},[],[],[],[],[],[]]