HW Override Default Sender Security & Risk Analysis

wordpress.org/plugins/hw-override-default-sender

Overrides WordPress default e-mail sender information (WordPress ) with information you provided.

10 active installs v1.0 PHP + WP 3.0+ Updated Feb 4, 2015
e-mailfromsender
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is HW Override Default Sender Safe to Use in 2026?

Generally Safe

Score 85/100

HW Override Default Sender has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 11yr ago
Risk Assessment

The security analysis of the "hw-override-default-sender" v1.0 plugin indicates a strong security posture based on the provided static analysis results. The plugin exhibits an extremely small attack surface, with no detected AJAX handlers, REST API routes, shortcodes, or cron events. Crucially, all detected entry points (of which there are none) are reported as protected. The code itself demonstrates adherence to good security practices, with no dangerous functions, no direct SQL queries (100% using prepared statements), and all outputs properly escaped. There are no file operations or external HTTP requests, further limiting potential attack vectors. The absence of any recorded vulnerabilities in its history, including CVEs of any severity, also points to a well-maintained and secure plugin.

While the plugin's current state appears very secure, the complete lack of any detected taint flows or even logged flows is unusual for a plugin that might interact with user input or external data. This could indicate a very simple functionality or, conversely, that the analysis was unable to fully trace all potential data flows. The absence of nonce checks and capability checks, while not immediately problematic given the zero attack surface, means that if functionality were to be added in the future that exposes entry points, these crucial security measures would be missing. However, based solely on the data provided for v1.0, the plugin presents a minimal risk.

Vulnerabilities
None known

HW Override Default Sender Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Version History

HW Override Default Sender Release Timeline

v1.0Current
Code Analysis
Analyzed Apr 16, 2026

HW Override Default Sender 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

HW Override Default Sender Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 3
actionphpmailer_inithw-override-default-sender.php:21
filterwp_mail_fromhw-override-default-sender.php:22
filterwp_mail_from_namehw-override-default-sender.php:23
Maintenance & Trust

HW Override Default Sender Maintenance & Trust

Maintenance Signals

WordPress version tested4.1.42
Last updatedFeb 4, 2015
PHP min version
Downloads1K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

HW Override Default Sender Developer Profile

Håkan Wennerberg

3 plugins · 1K total installs

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

How We Detect HW Override Default Sender

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

Asset Fingerprints

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about HW Override Default Sender