NearSt for WooCommerce Security & Risk Analysis

wordpress.org/plugins/nearst-for-woocommerce

NearSt helps brick-and-mortar shops get more footfall.

10 active installs v1.4.0 PHP 5.7+ WP 4.4+ Updated Mar 16, 2026
inventorylocalpoint-of-saleretailwoocommerce
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is NearSt for WooCommerce Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs Updated 5mo ago
Risk Assessment

The static analysis of the "nearst-for-woocommerce" v1.4.0 plugin reveals a generally positive security posture, with no detected AJAX handlers, REST API routes, or shortcodes that are unprotected. The complete absence of dangerous functions and the exclusive use of prepared statements for SQL queries are significant strengths. However, several concerns emerge from the analysis. The fact that 100% of the plugin's total outputs are not properly escaped presents a potential risk for cross-site scripting (XSS) vulnerabilities. Additionally, the presence of file operations and external HTTP requests without clear indications of sanitization or authentication checks in the static analysis warrants caution. The taint analysis, while not reporting critical or high severity flows, did identify four flows with unsanitized paths, which, combined with the lack of output escaping, could still lead to exploitable issues.

Key Concerns

  • Outputs not properly escaped
  • Taint flows with unsanitized paths
  • File operations without clear checks
  • External HTTP requests without clear checks
  • No nonce checks detected
  • No capability checks detected
Vulnerabilities
None known

NearSt for WooCommerce Security Vulnerabilities

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

NearSt for WooCommerce Release Timeline

v1.4.0Current
v1.3.3
v1.3.2
v1.3.0
v1.2.9
v1.2.7
v1.2.5
v1.2.4
v1.2.3
v1.2.2
v1.2.1
v1.2.0
v1.1.9
v1.1.8
v1.1.7
v1.1.6
v1.1.5
v1.1.4
v1.1.3
v1.1.2
Code Analysis
Analyzed Mar 17, 2026

NearSt for WooCommerce 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
2
Bundled Libraries
0

Output Escaping

0% escaped1 total outputs
Data Flows · Security
4 unsanitized

Data Flow Analysis

4 flows4 with unsanitized paths
redirect (includes\Redirect.php:19)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

NearSt for WooCommerce Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 8
filtercron_schedulesincludes\Cron.php:25
actionnearst_regular_uploadincludes\Cron.php:34
actionadmin_menuincludes\Options.php:25
actioninitincludes\Plugin.php:68
actionwp_headincludes\Plugin.php:69
actiontemplate_redirectincludes\Plugin.php:70
actionall_admin_noticesincludes\Requirements.php:33
actionplugins_loadednearst-for-woocommerce.php:18

Scheduled Events 1

nearst_regular_upload
Maintenance & Trust

NearSt for WooCommerce Maintenance & Trust

Maintenance Signals

WordPress version tested6.8.6
Last updatedMar 16, 2026
PHP min version5.7
Downloads3K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

NearSt for WooCommerce Developer Profile

NearSt

1 plugin · 10 total installs

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

How We Detect NearSt for WooCommerce

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/nearst-for-woocommerce/assets/
Version Parameters
nearst-for-woocommerce/nearst-for-woocommerce.php?ver=

HTML / DOM Fingerprints

Data Attributes
name="nearst"
FAQ

Frequently Asked Questions about NearSt for WooCommerce