WP Page Extension Security & Risk Analysis

wordpress.org/plugins/wp-page-extension

Converting an old HTML, PHP, or ASP site to WordPress? WP Page Extension will let you create pages inside of wordpress and give them any extension you …

80 active installs v1.1 PHP + WP 3.0+ Updated Aug 29, 2012
extensionfakehtmhtmlurl
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is WP Page Extension Safe to Use in 2026?

Generally Safe

Score 85/100

WP Page Extension has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 13yr ago
Risk Assessment

The 'wp-page-extension' v1.1 plugin exhibits a mixed security posture. On the positive side, it has a remarkably small attack surface with no identified AJAX handlers, REST API routes, shortcodes, or cron events, and importantly, no known CVEs in its history. This suggests a development team that is either very disciplined or has had limited exposure to security issues.

However, the static analysis reveals significant concerns. The complete lack of capability checks and nonce checks on any potential entry points is a major weakness. Coupled with the fact that 3 out of 3 analyzed taint flows have unsanitized paths and a 0% rate of proper output escaping, this indicates a high risk of various injection vulnerabilities, such as cross-site scripting (XSS) or potentially SQL injection if the raw SQL queries are not handled carefully in conjunction with the unsanitized inputs.

While the plugin has no recorded vulnerabilities, the code analysis signals are alarming and suggest potential vulnerabilities that may not have been discovered or reported yet. The high number of SQL queries, with only half using prepared statements, also adds to the risk, especially when combined with unsanitized inputs. The plugin's strengths lie in its limited attack surface and clean vulnerability history, but these are heavily overshadowed by the critical findings in the code analysis.

Key Concerns

  • Unsanitized paths in taint flows (High severity)
  • No capability checks
  • No nonce checks
  • SQL queries with prepared statements at 50%
  • No properly escaped output
Vulnerabilities
None known

WP Page Extension Security Vulnerabilities

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

WP Page Extension Code Analysis

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

SQL Query Safety

50% prepared16 total queries

Output Escaping

0% escaped7 total outputs
Data Flows
3 unsanitized

Data Flow Analysis

3 flows3 with unsanitized paths
check_url (wp-page_extension.php:234)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

WP Page Extension Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 5
actionadmin_initwp-page_extension.php:13
actiontemplate_redirectwp-page_extension.php:14
actionadd_meta_boxeswp-page_extension.php:16
actionwp_insert_postwp-page_extension.php:17
filteruser_trailingslashitwp-page_extension.php:18
Maintenance & Trust

WP Page Extension Maintenance & Trust

Maintenance Signals

WordPress version tested3.3.2
Last updatedAug 29, 2012
PHP min version
Downloads11K

Community Trust

Rating80/100
Number of ratings9
Active installs80
Developer Profile

WP Page Extension Developer Profile

Daddydesign

5 plugins · 240 total installs

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

How We Detect WP Page Extension

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

Asset Fingerprints

HTML / DOM Fingerprints

Data Attributes
name="fake_extension"id="fake_extension0"id="fake_extension1"id="fake_extension2"id="fake_extension3"id="fake_extension4"+2 more
FAQ

Frequently Asked Questions about WP Page Extension