No noopener noreferrer – Don’t add rel="noopener noreferrer" Security & Risk Analysis

wordpress.org/plugins/no-noopener-noreferrer-dont-add-relnoopener-noreferrer

Prevent Wordpress from adding noreferrer and noopener to external links.

300 active installs v1.0.0 PHP + WP 3.0+ Updated May 1, 2017
noopenernoreferrer
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is No noopener noreferrer – Don’t add rel="noopener noreferrer" Safe to Use in 2026?

Generally Safe

Score 85/100

No noopener noreferrer – Don’t add rel="noopener noreferrer" has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 8yr ago
Risk Assessment

The plugin "no-noopener-noreferrer-dont-add-relnoopener-noreferrer" v1.0.0 exhibits an exceptionally strong security posture based on the provided static analysis. The absence of any identified attack surface points, dangerous functions, file operations, or external HTTP requests is a significant strength. Furthermore, all SQL queries utilize prepared statements, and all output is properly escaped, indicating robust coding practices for data handling and presentation. The lack of any taint analysis findings further reinforces the impression of a secure codebase.

The vulnerability history being entirely clear, with no recorded CVEs, is a testament to the plugin's current stability and the absence of known security flaws. This, combined with the clean static analysis, suggests that the plugin is likely very well-written and developed with security in mind. However, the complete absence of nonces and capability checks, while not indicative of an immediate vulnerability in this specific analysis (due to the lack of an attack surface), does represent a potential area for concern if the plugin were to evolve and introduce new features that interact with user actions or sensitive data in the future. In its current state and version, the plugin appears to be highly secure.

Vulnerabilities
None known

No noopener noreferrer – Don’t add rel="noopener noreferrer" Security Vulnerabilities

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

No noopener noreferrer – Don’t add rel="noopener noreferrer" 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

No noopener noreferrer – Don’t add rel="noopener noreferrer" Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 1
filtertiny_mce_before_initnoopnoref.php:19
Maintenance & Trust

No noopener noreferrer – Don’t add rel="noopener noreferrer" Maintenance & Trust

Maintenance Signals

WordPress version tested4.7.32
Last updatedMay 1, 2017
PHP min version
Downloads5K

Community Trust

Rating80/100
Number of ratings4
Active installs300
Developer Profile

No noopener noreferrer – Don’t add rel="noopener noreferrer" Developer Profile

matthewtatumwordpress

1 plugin · 300 total installs

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

How We Detect No noopener noreferrer – Don’t add rel="noopener noreferrer"

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 No noopener noreferrer – Don’t add rel="noopener noreferrer"