Import WordPress 1.x Security & Risk Analysis

wordpress.org/plugins/import-wodpress-1x

Import WordPress 1.x The importers of WordPress 2.x includes two ways to import another WordPress blog, but the WP to WP importer works only if both v …

10 active installs v1.0 PHP + WP + Updated Sep 10, 2007
import
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Import WordPress 1.x Safe to Use in 2026?

Generally Safe

Score 85/100

Import WordPress 1.x has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 18yr ago
Risk Assessment

The "import-wordpress-1x" v1.0 plugin exhibits a mixed security posture. On the positive side, the plugin demonstrates good practices by not exposing any obvious attack surface points like AJAX handlers, REST API routes, or shortcodes without authentication checks. Furthermore, all SQL queries are prepared, and there are no known historical vulnerabilities or CVEs associated with this plugin, suggesting a generally stable development history.

However, several critical concerns arise from the static analysis. The presence of the "set_time_limit" function is a red flag as it can be exploited to extend execution time beyond intended limits, potentially leading to Denial of Service or resource exhaustion. More significantly, a complete lack of output escaping across all identified outputs is a major vulnerability. This means any data processed or displayed by the plugin is susceptible to Cross-Site Scripting (XSS) attacks, allowing attackers to inject malicious scripts into the user's browser.

While the absence of historical vulnerabilities is positive, it does not mitigate the immediate risks identified in the code. The plugin's strengths in attack surface reduction and SQL practices are significantly undermined by its critical flaws in output handling and the use of potentially dangerous functions. The overall recommendation is to use this plugin with extreme caution until these identified vulnerabilities are addressed.

Key Concerns

  • Output not properly escaped
  • Dangerous function used (set_time_limit)
  • No nonce checks
  • No capability checks
Vulnerabilities
None known

Import WordPress 1.x Security Vulnerabilities

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

Import WordPress 1.x Release Timeline

No version history available.
Code Analysis
Analyzed Apr 16, 2026

Import WordPress 1.x Code Analysis

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

Dangerous Functions Found

set_time_limitif(isset($_POST['moretime'])) set_time_limit(180);wordpress1x.php:104

Output Escaping

0% escaped3 total outputs
Attack Surface

Import WordPress 1.x Attack Surface

Entry Points0
Unprotected0
Maintenance & Trust

Import WordPress 1.x Maintenance & Trust

Maintenance Signals

WordPress version tested2.2.1
Last updatedSep 10, 2007
PHP min version
Downloads3K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Import WordPress 1.x Developer Profile

caugb

3 plugins · 40 total installs

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

How We Detect Import WordPress 1.x

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

Asset Fingerprints

HTML / DOM Fingerprints

CSS Classes
wraptohideupdatedfadenarrow
Data Attributes
id="wrap_iwp1x"id="message"class="updated fade"id="blog_url"id="create_cat"id="inc_comments"+1 more
JS Globals
msgiwp1x_direlsmsgelrefel
FAQ

Frequently Asked Questions about Import WordPress 1.x