Remember Me Security & Risk Analysis

wordpress.org/plugins/remember-me

Plays the chorus of Remember Me from Disney's Coco everytime you check Remember Me on the WordPress login page.

0 active installs v1.0.1 PHP 5.4+ WP 4.8+ Updated Sep 20, 2022
login
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Remember Me Safe to Use in 2026?

Generally Safe

Score 85/100

Remember Me has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 3yr ago
Risk Assessment

The 'remember-me' plugin v1.0.1 demonstrates a generally strong security posture based on the provided static analysis. The absence of identified attack surface points such as AJAX handlers, REST API routes, shortcodes, and cron events significantly reduces the potential for external exploitation. Furthermore, the code analysis shows no dangerous functions, file operations, or external HTTP requests, and all SQL queries utilize prepared statements, which are excellent security practices. The lack of any recorded vulnerabilities in its history further bolsters this positive assessment.

However, a significant concern arises from the output escaping analysis, where 100% of the identified outputs are not properly escaped. This could lead to Cross-Site Scripting (XSS) vulnerabilities if any user-supplied data is reflected directly in the output without proper sanitization. While the plugin's attack surface appears minimal and there are no identified taint flows, this unescaped output presents a clear risk that needs to be addressed. The lack of nonce and capability checks, while not directly exploitable given the current attack surface, could become a vulnerability if new entry points are introduced in future versions without adequate security measures.

In conclusion, 'remember-me' v1.0.1 exhibits good practices in its limited attack surface and SQL handling. The primary weakness lies in the complete lack of output escaping, which is a critical oversight for preventing XSS. While the vulnerability history is clean, the unescaped outputs represent a potential area for exploitation. Addressing the output escaping issue should be the immediate priority for improving the plugin's security.

Key Concerns

  • Unescaped output detected
Vulnerabilities
None known

Remember Me Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Code Analysis
Analyzed Mar 17, 2026

Remember Me Code Analysis

Dangerous Functions
0
Raw SQL Queries
0
0 prepared
Unescaped Output
2
0 escaped
Nonce Checks
0
Capability Checks
0
File Operations
0
External Requests
0
Bundled Libraries
0

Output Escaping

0% escaped2 total outputs
Attack Surface

Remember Me Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 2
actionlogin_enqueue_scriptsremember-me.php:30
actionlogin_footerremember-me.php:43
Maintenance & Trust

Remember Me Maintenance & Trust

Maintenance Signals

WordPress version tested6.0.11
Last updatedSep 20, 2022
PHP min version5.4
Downloads1K

Community Trust

Rating0/100
Number of ratings0
Active installs0
Developer Profile

Remember Me Developer Profile

Joe Fusco

4 plugins · 2K total installs

86
trust score
Avg Security Score
89/100
Avg Patch Time
30 days
View full developer profile
Detection Fingerprints

How We Detect Remember Me

Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.

Asset Fingerprints

Asset Paths
/wp-content/plugins/remember-me/assets/scripts/remember-me.js/wp-content/plugins/remember-me/assets/audio/remember-me.ogg/wp-content/plugins/remember-me/assets/audio/remember-me.mp3
Script Paths
/wp-content/plugins/remember-me/assets/scripts/remember-me.js
Version Parameters
remember-me/assets/scripts/remember-me.js?ver=1.0.1

HTML / DOM Fingerprints

Shortcode Output
<audio id="remembermeaudio"><source src="<source src="</audio>
FAQ

Frequently Asked Questions about Remember Me