
Last Viewed Posts by WPBeginner Security & Risk Analysis
wordpress.org/plugins/last-viewed-postsThis shows your site's visitors a personalized list of posts and pages they have recently viewed.
Is Last Viewed Posts by WPBeginner Safe to Use in 2026?
Generally Safe
Score 88/100Last Viewed Posts by WPBeginner has a strong security track record. Known vulnerabilities have been patched promptly. It's a solid choice for most WordPress installations.
The "last-viewed-posts" plugin v1.0.2 exhibits a mixed security posture. On the positive side, the static analysis shows no identified entry points such as AJAX handlers, REST API routes, or shortcodes that are directly exposed without authentication. The code also demonstrates good practices with 100% of SQL queries using prepared statements and no identified dangerous functions or file operations. However, a significant concern is the moderate output escaping, with only 42% of outputs properly escaped, which could lead to cross-site scripting (XSS) vulnerabilities if data is not handled carefully before being displayed.
The plugin's vulnerability history is a major red flag. With two known CVEs, including one critical and one medium, and a recent vulnerability discovered in December 2024, it indicates a pattern of past security weaknesses. The common vulnerability types of Improper Access Control and Deserialization of Untrusted Data suggest that the plugin has historically struggled with securely handling user input and managing permissions. While there are currently no unpatched vulnerabilities, the existence of past critical issues and the lack of any capability checks or nonce checks in the static analysis are concerning, especially given the historical context.
In conclusion, while the current static analysis does not reveal immediate, exploitable attack vectors, the plugin's past vulnerability history, particularly critical ones, combined with the moderate output escaping and absence of capability checks, presents a significant risk. Users should exercise caution and consider whether the benefits of the plugin outweigh the potential risks and the ongoing need for vigilant monitoring and potential future patching.
Key Concerns
- Unescaped output detected (58% not escaped)
- Past critical vulnerability (1)
- Past medium vulnerability (1)
- No capability checks
- No nonce checks
Last Viewed Posts by WPBeginner Security Vulnerabilities
CVEs by Year
Severity Breakdown
2 total CVEs
Last Viewed Posts by WPBeginner <= 1.0.1 - Unauthenticated Sensitive Information Exposure
Last Viewed Posts by WPBeginner <= 1.0.0 - Unauthenticated PHP Object Injection
Last Viewed Posts by WPBeginner Release Timeline
Last Viewed Posts by WPBeginner Code Analysis
Output Escaping
Last Viewed Posts by WPBeginner Attack Surface
WordPress Hooks 5
Maintenance & Trust
Last Viewed Posts by WPBeginner Maintenance & Trust
Maintenance Signals
Community Trust
Last Viewed Posts by WPBeginner Alternatives
Last Viewed Posts by WPBeginner Developer Profile
1 plugin · 500 total installs
How We Detect Last Viewed Posts by WPBeginner
Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.
Asset Fingerprints
/wp-content/plugins/last-viewed-posts/assets/index.js/wp-content/plugins/last-viewed-posts/assets/index.jsam.view_last_posts?ver=am.view_last_posts?ver=HTML / DOM Fingerprints
am.last-viewed-posts.display-noneviewed_postsamViewLastPosts<ul class="viewed_posts am.last-viewed-posts.display-none"></ul><script>
( 'amViewLastPosts' in window && 'script' in amViewLastPosts && amViewLastPosts.script(amViewLastPosts.settings, window, document) )
</script>