Permalink History Security & Risk Analysis

wordpress.org/plugins/permalink-history

Saves the history of your WordPress site permalinks and provides automatic redirects.

50 active installs v2.0.3 PHP + WP 5.0+ Updated Feb 10, 2026
backuphistorypermalinkprotocolseo
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is Permalink History Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs Updated 1mo ago
Risk Assessment

The "permalink-history" plugin v2.0.3 exhibits a mixed security posture. While it shows good practices by avoiding dangerous functions, file operations, and external HTTP requests, and largely using prepared statements for SQL queries, significant security concerns exist. The presence of two AJAX handlers without authentication checks presents a direct attack vector that could be exploited by unauthenticated users. Furthermore, the lack of nonce checks on these AJAX endpoints exacerbates this risk, as it makes them susceptible to Cross-Site Request Forgery (CSRF) attacks. The code also shows only 52% of outputs being properly escaped, indicating a potential for Cross-Site Scripting (XSS) vulnerabilities. The plugin's vulnerability history is clean, with no recorded CVEs, which is a positive indicator of past security diligence. However, this clean history does not negate the immediate risks identified in the current static analysis. The overall conclusion is that while the plugin has some good security foundations, the unprotected AJAX endpoints and potential for unescaped output are critical weaknesses that require immediate attention.

Key Concerns

  • AJAX handlers without auth checks
  • Output escaping is insufficient (52% proper)
  • No nonce checks on AJAX handlers
Vulnerabilities
None known

Permalink History Security Vulnerabilities

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

Permalink History Code Analysis

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

SQL Query Safety

89% prepared19 total queries

Output Escaping

52% escaped21 total outputs
Attack Surface
2 unprotected

Permalink History Attack Surface

Entry Points2
Unprotected2

AJAX Handlers 2

authwp_ajax_permalink_historyclasses\Ajax.php:9
noprivwp_ajax_permalink_historyclasses\Ajax.php:10
WordPress Hooks 12
actioninitclasses\Components\Plugin.php:30
actioninitclasses\Gutenberg.php:11
actionenqueue_block_editor_assetsclasses\Gutenberg.php:12
actionph_migrate_register_field_handlersclasses\Migrate.php:16
actionsave_postclasses\Post.php:16
actionget_headerclasses\Post.php:17
actiondeleted_postclasses\Post.php:18
actiontemplate_redirectclasses\Redirects.php:22
actionrest_api_initclasses\REST.php:13
actionadmin_initclasses\Settings.php:16
actionedit_termsclasses\TermTaxonomy.php:17
actionget_headerclasses\TermTaxonomy.php:18
Maintenance & Trust

Permalink History Maintenance & Trust

Maintenance Signals

WordPress version tested6.8.5
Last updatedFeb 10, 2026
PHP min version
Downloads2K

Community Trust

Rating0/100
Number of ratings0
Active installs50
Developer Profile

Permalink History Developer Profile

EdwardBock

22 plugins · 2K total installs

72
trust score
Avg Security Score
90/100
Avg Patch Time
107 days
View full developer profile
Detection Fingerprints

How We Detect Permalink History

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/permalink-history/dist/gutenberg.ts.js
Script Paths
/wp-content/plugins/permalink-history/dist/gutenberg.ts.js

HTML / DOM Fingerprints

REST Endpoints
/wp-json/permalink-history/v1/posts/wp-json/permalink-history/v1/posts/(?P<content_id>\d+)
FAQ

Frequently Asked Questions about Permalink History