[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fIH5NzX_F6HErb73P6QSOYkaLlowD6vHSEPHRobZ4Knk":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":37,"analysis":38,"fingerprints":89},"remove-revision-dummy-content-wp","Remove Revision Dummy Content WP","1.1.0","Satish Dharavia","https:\u002F\u002Fprofiles.wordpress.org\u002Fsatishnavjivan\u002F","\u003Cp>Remove Revision and Dummy Content\u003C\u002Fp>\n\u003Cp>Where you can scheck  options\u003C\u002Fp>\n\u003Col>\n\u003Cli>\n\u003Cp>Take a database bakup.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Check before database size.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Remove Revision and Dummy Content.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Check after database size.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>In order to configure settings, navigate to \u003Cstrong>[ WordPress Admin -> Settings -> Remove revision history ]\u003C\u002Fstrong>, where you can see options:\u003C\u002Fp>\n\u003Cp>List of Revision and post meta data\u003C\u002Fp>\n\u003Ch4>NOTE\u003C\u002Fh4>\n\u003Cp>We have this plugin compatible gutenberg.\u003C\u002Fp>\n","Remove Revision and Dummy Content",0,831,"2023-05-30T13:17:00.000Z","6.2.9","5.3.2","",[18,19,20,21,22],"dummy-post-metadata","dummy-test","remove-dummy-content","remove-history","remove-revision","http:\u002F\u002Fwordpress.org\u002Fplugins\u002Fremove-revision-dummy-content-wp\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fremove-revision-dummy-content-wp.zip",85,null,"2026-03-15T15:16:48.613Z",[],{"slug":30,"display_name":31,"profile_url":8,"plugin_count":32,"total_installs":11,"avg_security_score":33,"avg_patch_time_days":34,"trust_score":35,"computed_at":36},"satishnavjivan","satish",2,93,30,89,"2026-04-04T19:08:38.195Z",[],{"attackSurface":39,"codeSignals":66,"taintFlows":79,"riskAssessment":80,"analyzedAt":88},{"hooks":40,"ajaxHandlers":54,"restRoutes":63,"shortcodes":64,"cronEvents":65,"entryPointCount":32,"unprotectedCount":11},[41,47,50],{"type":42,"name":43,"callback":44,"file":45,"line":46},"action","admin_notices","rrdcw_admin_notice__success","remove-revision-dummy-content-wp.php",32,{"type":42,"name":43,"callback":48,"file":45,"line":49},"rrdcw_my_error_notice",50,{"type":42,"name":51,"callback":52,"file":45,"line":53},"admin_menu","rrdcw_register_submenu_page",51,[55,60],{"action":56,"nopriv":57,"callback":56,"hasNonce":58,"hasCapCheck":57,"file":45,"line":59},"rrdcw_remove_revision_query_run",false,true,256,{"action":61,"nopriv":57,"callback":61,"hasNonce":58,"hasCapCheck":57,"file":45,"line":62},"rrdcw_remove_revision_query_run_rb",281,[],[],[],{"dangerousFunctions":67,"sqlUsage":68,"outputEscaping":71,"fileOperations":11,"externalRequests":11,"nonceChecks":32,"capabilityChecks":11,"bundledLibraries":78},[],{"prepared":69,"raw":11,"locations":70},5,[],{"escaped":11,"rawEcho":32,"locations":72},[73,76],{"file":45,"line":74,"context":75},164,"raw output",{"file":45,"line":77,"context":75},242,[],[],{"summary":81,"deductions":82},"The \"remove-revision-dummy-content-wp\" plugin v1.1.0 exhibits a generally strong security posture, with several positive attributes. The absence of known CVEs and a clean vulnerability history suggest a well-maintained and secure codebase over time.  Furthermore, the plugin diligently uses prepared statements for all SQL queries, indicating a good defense against SQL injection.  All identified entry points (AJAX handlers) include nonce checks, a crucial step in preventing Cross-Site Request Forgery (CSRF) attacks.\n\nDespite these strengths, there are areas for improvement. The most significant concern is the lack of output escaping on all identified output points. This could potentially lead to Cross-Site Scripting (XSS) vulnerabilities if user-supplied data is directly rendered without proper sanitization. Additionally, while capability checks are absent on the AJAX handlers, the presence of nonce checks mitigates some of the risk, but robust capability checks would offer a more comprehensive security layer against unauthorized access. The taint analysis showing zero flows is also a positive indicator, suggesting no obvious vulnerabilities were detected through that methodology.\n\nIn conclusion, the plugin has a solid foundation with its use of prepared statements and nonce checks. However, the unescaped output is a notable weakness that requires immediate attention to prevent XSS attacks. Strengthening authorization by implementing capability checks on its AJAX handlers would further enhance its security. The clean vulnerability history is a strong positive signal that the developers are committed to security, but vigilance remains essential.",[83,86],{"reason":84,"points":85},"Output escaping is not implemented",8,{"reason":87,"points":69},"AJAX handlers lack capability checks","2026-03-17T06:33:08.228Z",{"wat":90,"direct":96},{"assetPaths":91,"generatorPatterns":93,"scriptPaths":94,"versionParams":95},[92],"\u002Fwp-content\u002Fplugins\u002Fremove-revision-dummy-content-wp\u002F",[],[],[],{"cssClasses":97,"htmlComments":99,"htmlAttributes":100,"restEndpoints":106,"jsGlobals":107,"shortcodeOutput":110},[98],"rrdcw_snv",[],[101,102,103,104,105],"id=\"rrhw\"","class=\"wrap\"","id=\"icon-settings\"","class=\"icon32\"","class=\"querycode\"",[],[108,109],"jQuery","admin_url",[]]