JSM User Locale Selector Security & Risk Analysis

wordpress.org/plugins/jsm-user-locale

Add a quick and easy user locale / language selector in the WordPress admin back-end and front-end toolbar menus.

20 active installs v2.2.1 PHP 7.4.33+ WP 6.0+ Updated Mar 25, 2026
languagelocalepolylangselectuser
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is JSM User Locale Selector Safe to Use in 2026?

Generally Safe

Score 100/100

JSM User Locale Selector has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 1mo ago
Risk Assessment

The jsm-user-locale plugin v2.2.1 demonstrates a strong security posture based on the provided static analysis and vulnerability history. There are no identified CVEs, and the code analysis reveals no dangerous functions, file operations, external HTTP requests, or SQL queries that are not properly prepared. Output escaping is fully implemented, and there are no untrusted external library dependencies. The plugin also appears to have a minimal attack surface, with zero identified entry points like AJAX handlers, REST API routes, or shortcodes.

Despite the excellent general security practices, there are two concerning "flows with unsanitized paths" identified in the taint analysis. While these did not escalate to critical or high severity, they indicate potential pathways where untrusted data could be handled without sufficient sanitization, which warrants further investigation by the developer. The complete absence of nonce and capability checks, while not directly exploitable given the zero attack surface, suggests a lack of defensive programming that could become a liability if new entry points are introduced in future versions.

Overall, jsm-user-locale v2.2.1 is a highly secure plugin with a clean vulnerability history and robust coding practices. The primary concern lies with the two identified unsanitized paths, which, although not currently critical, should be addressed to further harden the plugin against potential future threats.

Key Concerns

  • Flows with unsanitized paths
  • No nonce checks
  • No capability checks
Vulnerabilities
None known

JSM User Locale Selector Security Vulnerabilities

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

JSM User Locale Selector Release Timeline

v2.2.1Current
Code Analysis
Analyzed Mar 16, 2026

JSM User Locale Selector Code Analysis

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

Output Escaping

100% escaped1 total outputs
Data Flows · Security
2 unsanitized

Data Flow Analysis

2 flows2 with unsanitized paths
update_user_locale (jsm-user-locale.php:267)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

JSM User Locale Selector Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 4
actioninitjsm-user-locale.php:216
actionplugins_loadedjsm-user-locale.php:251
actionadmin_bar_menujsm-user-locale.php:252
actioninitjsm-user-locale.php:256
Maintenance & Trust

JSM User Locale Selector Maintenance & Trust

Maintenance Signals

WordPress version tested6.9.4
Last updatedMar 25, 2026
PHP min version7.4.33
Downloads6K

Community Trust

Rating100/100
Number of ratings5
Active installs20
Developer Profile

JSM User Locale Selector Developer Profile

JS Morisset

31 plugins · 32K total installs

93
trust score
Avg Security Score
99/100
Avg Patch Time
12 days
View full developer profile
Detection Fingerprints

How We Detect JSM User Locale Selector

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/jsm-user-locale/js/user-locale.js
Script Paths
jsm-user-locale/js/user-locale.js
Version Parameters
jsm-user-locale/js/user-locale.js?ver=

HTML / DOM Fingerprints

JS Globals
JsmUserLocale
FAQ

Frequently Asked Questions about JSM User Locale Selector