Permalinks Moved Permanently Security & Risk Analysis

wordpress.org/plugins/permalinks-moved-permanently

If you just migrated your Wordpress blog from one permalink structure to another, and you don't want to lose Pagerank or traffic that accesses yo …

700 active installs v1.3 PHP + WP 2.0+ Updated Nov 28, 2017
301404migratemovepermalinks
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Permalinks Moved Permanently Safe to Use in 2026?

Generally Safe

Score 85/100

Permalinks Moved Permanently 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 "permalinks-moved-permanently" v1.3 plugin exhibits a strong adherence to general WordPress security best practices, as indicated by a lack of known vulnerabilities, a clean attack surface, and proper output escaping. The absence of AJAX handlers, REST API routes, shortcodes, and cron events significantly limits potential entry points for attackers. Furthermore, the plugin doesn't appear to engage in dangerous functions, file operations, external HTTP requests, or rely on bundled libraries that could introduce known weaknesses.

However, the static analysis reveals two critical concerns regarding data flow. Two taint flows were identified with unsanitized paths, suggesting that user-supplied data might be processed in a way that could lead to injection vulnerabilities if not handled correctly downstream, despite the absence of direct SQL injection in the analyzed code. While there is only one SQL query, it is not using prepared statements, which represents a potential risk for SQL injection if the query's parameters are not meticulously sanitized. The lack of nonce and capability checks, although seemingly less impactful given the limited attack surface, are generally considered good security practices for any plugin.

In conclusion, the plugin's strengths lie in its minimal attack surface and good output escaping. The primary weaknesses revolve around potential data handling issues in taint flows and the use of raw SQL queries, which, while not resulting in documented vulnerabilities to date, represent an area for improvement to enhance its overall security posture and proactively prevent future exploits.

Key Concerns

  • Unsanitized taint flows (2)
  • SQL queries not using prepared statements
  • Missing nonce checks
  • Missing capability checks
Vulnerabilities
None known

Permalinks Moved Permanently Security Vulnerabilities

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

Permalinks Moved Permanently Code Analysis

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

SQL Query Safety

0% prepared1 total queries
Data Flows
2 unsanitized

Data Flow Analysis

2 flows2 with unsanitized paths
bas_permalink_moved_permanently (permalinks-moved-permanently.php:40)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Permalinks Moved Permanently Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 1
actiontemplate_redirectpermalinks-moved-permanently.php:56
Maintenance & Trust

Permalinks Moved Permanently Maintenance & Trust

Maintenance Signals

WordPress version tested2.6
Last updatedNov 28, 2017
PHP min version
Downloads86K

Community Trust

Rating0/100
Number of ratings0
Active installs700
Developer Profile

Permalinks Moved Permanently Developer Profile

microkid

2 plugins · 710 total installs

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

How We Detect Permalinks Moved Permanently

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 Permalinks Moved Permanently