Disable Autocomplete Security & Risk Analysis

wordpress.org/plugins/disable-autocomplete

Disable the browser's ability to autofill forms and input fields. Ideal for forms with sensitive information and provides extra level of form sub …

100 active installs v1.0 PHP + WP 3.0+ Updated Unknown
autofilldisable-autofilldisable-form-autofillform-autofillinput-autofill
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Disable Autocomplete Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs
Risk Assessment

The "disable-autocomplete" v1.0 plugin exhibits a strong security posture based on the provided static analysis. The absence of any identified AJAX handlers, REST API routes, shortcodes, or cron events significantly limits its attack surface. Furthermore, the code analysis reveals no dangerous functions, SQL queries are exclusively using prepared statements, all output is properly escaped, and there are no file operations or external HTTP requests. The lack of any recorded vulnerabilities in its history further reinforces this positive assessment.

However, the complete absence of nonce checks and capability checks is a notable concern. While the current attack surface is zero, any future functionality added without proper authentication and authorization mechanisms could introduce significant security risks. The plugin's simplicity and its current lack of interaction points are its greatest strengths, but this also means that the security model for potential future expansions is untested and potentially absent.

In conclusion, the plugin is currently secure due to its minimal functionality and attack surface. The development team has followed good practices regarding SQL and output escaping. The primary weakness lies in the absence of built-in security checks like nonces and capability checks, which, if not addressed when adding features, could lead to vulnerabilities in the future. As it stands, the immediate risk is low, but its long-term security is dependent on future development practices.

Key Concerns

  • Missing nonce checks
  • Missing capability checks
Vulnerabilities
None known

Disable Autocomplete Security Vulnerabilities

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

Disable Autocomplete Code Analysis

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

Disable Autocomplete Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 1
actionwp_footerclasses\class-da-scripts.php:12
Maintenance & Trust

Disable Autocomplete Maintenance & Trust

Maintenance Signals

WordPress version tested4.5.33
Last updatedUnknown
PHP min version
Downloads4K

Community Trust

Rating60/100
Number of ratings4
Active installs100
Developer Profile

Disable Autocomplete Developer Profile

Andrew Gunn

9 plugins · 1K total installs

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

How We Detect Disable Autocomplete

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

Asset Fingerprints

HTML / DOM Fingerprints

Shortcode Output
<script type="text/javascript"> //jQuery(document).ready(function($) { jQuery(document).ready(function($){ if ($.browser.chrome) { //autcomplete_false(); $("input").each(function() { $(this).attr('autocomplete', 'false'); //FALSE AS OF 2015 }); // .each $("form").each(function() { $(this).attr('autocomplete', 'false'); //FALSE AS OF 2015 }); // .each } else { $("input").each(function() { $(this).attr('autocomplete', 'off'); }); // .each $("form").each(function() { $(this).attr('autocomplete', 'off'); }); // .each } }); </script>
FAQ

Frequently Asked Questions about Disable Autocomplete