Store Directory Security & Risk Analysis

wordpress.org/plugins/store-directory

A simple, flexible plugin for keeping a store/location directory and searching for them by radius.

10 active installs v0.1 PHP + WP 3.0+ Updated Jan 3, 2014
directorygoogle-mapslocationmapsstore
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Store Directory Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 12yr ago
Risk Assessment

The "store-directory" plugin v0.1 exhibits an excellent security posture based on the provided static analysis. There are no identified entry points for external interaction (AJAX, REST API, shortcodes, cron), eliminating many common attack vectors. The code also demonstrates strong security practices with a complete absence of dangerous functions, secure SQL query handling using prepared statements, and a high percentage of properly escaped output. File operations and external HTTP requests are also not present, further reducing the attack surface.

The vulnerability history is equally positive, with zero known CVEs, indicating a strong track record. This suggests diligent development and a lack of previously discovered exploitable flaws. While the taint analysis shows zero flows, this is likely due to the limited attack surface identified in the static analysis. It's important to note that the absence of nonce and capability checks on the zero identified entry points isn't a direct risk given their absence, but it does mean that if any entry points were to be introduced in the future without these checks, it would be a significant oversight.

Overall, "store-directory" v0.1 appears to be a very secure plugin. Its strengths lie in its minimal attack surface and robust coding practices. The primary area for continued vigilance would be to ensure that any future expansions of functionality include appropriate authentication and authorization checks, even if none are currently necessary.

Key Concerns

  • No nonce checks on entry points
  • No capability checks on entry points
  • Unescaped output (12% of total)
Vulnerabilities
None known

Store Directory Security Vulnerabilities

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

Store Directory Release Timeline

v0.1Current
Code Analysis
Analyzed Apr 16, 2026

Store Directory Code Analysis

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

Output Escaping

88% escaped16 total outputs
Attack Surface

Store Directory Attack Surface

Entry Points0
Unprotected0
Maintenance & Trust

Store Directory Maintenance & Trust

Maintenance Signals

WordPress version tested3.7.41
Last updatedJan 3, 2014
PHP min version
Downloads2K

Community Trust

Rating100/100
Number of ratings1
Active installs10
Developer Profile

Store Directory Developer Profile

Matthew Boynes

8 plugins · 8K total installs

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

How We Detect Store Directory

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/store-directory/css/store-directory.css/wp-content/plugins/store-directory/js/store-directory.js
Script Paths
/wp-content/plugins/store-directory/js/store-directory.js
Version Parameters
store-directory/css/store-directory.css?ver=store-directory/js/store-directory.js?ver=

HTML / DOM Fingerprints

CSS Classes
store-directory
JS Globals
storeDirectoryWPSD_URL
FAQ

Frequently Asked Questions about Store Directory