Spots Import/Export Security & Risk Analysis

wordpress.org/plugins/spots-importexport

** NOTE I have not had a use case for this plugin for a couple years. Keeping it for posterity here. If you would like to take over development let me …

10 active installs v0.7.2 PHP + WP 3.0.1+ Updated Unknown
exportexporterimportimporterspots
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is Spots Import/Export Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs
Risk Assessment

The "spots-importexport" plugin version 0.7.2 exhibits a generally strong security posture based on the provided static analysis. The absence of any AJAX handlers, REST API routes, shortcodes, or cron events significantly limits the plugin's attack surface. Furthermore, the code analysis reveals no dangerous functions, external HTTP requests, or unsanitized taint flows, which are positive indicators. The fact that all SQL queries utilize prepared statements is also a commendable security practice, mitigating the risk of SQL injection vulnerabilities.

However, there are notable concerns. The analysis indicates that 100% of observed output is not properly escaped. This is a critical weakness that could lead to Cross-Site Scripting (XSS) vulnerabilities if user-supplied data is displayed directly in the output without proper sanitization. Additionally, the complete absence of nonce and capability checks across all entry points, although the attack surface is currently zero, means that any future additions or modifications that introduce new entry points would be inherently insecure by default. The plugin's vulnerability history is clean, with no recorded CVEs, which is a positive sign but does not negate the immediate risks identified in the code analysis.

In conclusion, while the plugin benefits from a minimal attack surface and secure handling of database queries, the lack of output escaping and the absence of authorization checks are significant security flaws that require immediate attention. The absence of historical vulnerabilities is encouraging, but the current code presents clear risks that must be addressed to ensure user security.

Key Concerns

  • All output is unescaped
  • No nonce checks on entry points
  • No capability checks on entry points
Vulnerabilities
None known

Spots Import/Export Security Vulnerabilities

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

Spots Import/Export Code Analysis

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

Output Escaping

0% escaped1 total outputs
Attack Surface

Spots Import/Export Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 2
actioninitspots-imexport.php:11
actionadmin_menuspots-imexport.php:39
Maintenance & Trust

Spots Import/Export Maintenance & Trust

Maintenance Signals

WordPress version tested4.8.28
Last updatedUnknown
PHP min version
Downloads2K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Spots Import/Export Developer Profile

Ben Lobaugh (blobaugh)

11 plugins · 11K total installs

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

How We Detect Spots Import/Export

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/spots-importexport/imex_menu_page.php

HTML / DOM Fingerprints

CSS Classes
spots-imex-menu-page
FAQ

Frequently Asked Questions about Spots Import/Export