
Recent Archive More Widget Security & Risk Analysis
wordpress.org/plugins/recent-archive-more-widget'Recent Archive More Widget' displays posts, not listed on page content area on the widget area of the sidebar of category archive page.
Is Recent Archive More Widget Safe to Use in 2026?
Generally Safe
Score 85/100Recent Archive More Widget has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.
The "recent-archive-more-widget" v1.1 plugin exhibits a strong security posture based on the provided static analysis. The absence of AJAX handlers, REST API routes, shortcodes, and cron events significantly limits its attack surface. Furthermore, the plugin demonstrates good coding practices by exclusively using prepared statements for SQL queries and avoiding dangerous functions, file operations, and external HTTP requests. The lack of recorded vulnerabilities in its history also suggests a history of secure development and maintenance.
However, a notable concern is the low percentage of properly escaped output (20%). This indicates a potential for cross-site scripting (XSS) vulnerabilities, where untrusted data might be rendered directly in the browser without proper sanitization. While the taint analysis found no specific issues, the lack of comprehensive output escaping remains a significant weakness that could be exploited if any user-supplied data finds its way into an output context.
In conclusion, the plugin is generally well-secured with a limited attack surface and good SQL handling. The primary area for improvement and a source of moderate risk is the insufficient output escaping, which warrants careful attention to prevent potential XSS vulnerabilities. The clean vulnerability history is a positive indicator but does not negate the identified code-level risk.
Key Concerns
- Insufficient output escaping
Recent Archive More Widget Security Vulnerabilities
Recent Archive More Widget Code Analysis
Output Escaping
Recent Archive More Widget Attack Surface
WordPress Hooks 7
Maintenance & Trust
Recent Archive More Widget Maintenance & Trust
Maintenance Signals
Community Trust
Recent Archive More Widget Alternatives
Smart Archive Page Remove
smart-archive-page-remove
Completely remove unwanted Archive Pages from your Blog
Archive Control
archive-control
Quickly customize your custom post type and taxonomy archives with a custom headline, image, and editable content. Modify order and pagination.
Hide Archive Label
hide-archive-label
Hide Archive Label is a free WordPress plugin to hide or remove archive page title prefixes such as “Category:”, “Tags:”, “Author:”, and more.
Archive Page
archive-page
Make archive page easily with full customize and in all languages of the world.
Post Type Archive Pages
post-type-archive-pages
Place the archive pages for your post types in the structure of your content pages. The power of pages and post types combined!
Recent Archive More Widget Developer Profile
3 plugins · 20 total installs
How We Detect Recent Archive More Widget
Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.
Asset Fingerprints
/wp-content/plugins/recent-archive-more-widget/css/tp_style.cssHTML / DOM Fingerprints
recent_archivearchive-thumbnailarchive-post-titlerecent-archive-sidebar<!--
{someone posted this on a forum: i decided to make this plugin, got it ready 17hrs later }
The message from the original seeker
"[I am in the process of finding a plugin that could achieve as the following:
- Show the posts in in widget area like normal plugin that could show recent posts and has filters the same.
- Filter to show only posts in specific category if it's on that category archive
- If the archive show for example 5 posts that widget must not show those posts but show others.
It's hard to explain myself.]"
-->/*===---===-0--===--=-----=======---999---===============================
+Another way to acheive what i have below:
+ get_option('posts_per_page'); and set it as offset for the query
= below...hahaha... didn't like that idea at first..
= it goes like this
= 'offset' => (int)get_option('posts_per_page'),
=
then it came like this:: Thought about the loophole(no p intended)
= what if the page is using a custom query..
= Don't mind me. i'm hypersensitive.
=
=
=-=--0r0r0r0r0000r0r00r90f0f09foflfkrkfkfkrjfkekdjdkd==================== */id="recent_archive_post"class="recent-archive-sidebar"g_post_id