FrenchMap Security & Risk Analysis

wordpress.org/plugins/frenchmap

Affichez une carte de France interactive simple dans votre contenu !

60 active installs v1.0.1 PHP 5.6.20+ WP 5.3+ Updated Nov 10, 2023
cartecarte-de-francecarte-des-departements-francaiscarte-interactivefrance
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is FrenchMap Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 2yr ago
Risk Assessment

The "frenchmap" plugin v1.0.1 exhibits a generally strong security posture based on the provided static analysis. The absence of direct SQL queries, the heavy reliance on prepared statements, and the high percentage of properly escaped output suggest good development practices regarding common web vulnerabilities. Furthermore, the plugin has no recorded vulnerabilities (CVEs), indicating a history of stable and secure operation. This lack of historical issues, combined with the clean code signals, paints a picture of a well-maintained and secure plugin.

However, there are areas that warrant attention. The static analysis reveals a concerning lack of capability checks and nonce checks. This means that certain functionalities, even if not directly exposed via AJAX or REST API without authentication, might be callable without proper authorization verification. The presence of a shortcode as an entry point, while not explicitly flagged as unprotected, coupled with the missing capability checks, represents a potential vector for unauthorized access or manipulation if not handled with care within the shortcode's logic.

Taint analysis did not reveal any critical or high severity issues, which is positive. However, it's important to note that the taint analysis covered 0 flows, suggesting this might be an incomplete analysis or that the plugin's functionality is very limited. The sole file operation also needs careful scrutiny, as file operations, even if seemingly benign, can become vulnerabilities if not properly secured against unauthorized access or modification.

In conclusion, while "frenchmap" v1.0.1 benefits from a clean vulnerability history and good practices in SQL and output handling, the absence of capability and nonce checks is a significant weakness. This, along with the single file operation and limited taint analysis scope, suggests that while the plugin may be secure in its current state, there's room for improvement to harden its defenses against potential future threats or misconfigurations.

Key Concerns

  • Missing nonce checks
  • Missing capability checks
  • Single file operation
  • Limited taint analysis scope (0 flows)
Vulnerabilities
None known

FrenchMap Security Vulnerabilities

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

FrenchMap Code Analysis

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

Output Escaping

82% escaped17 total outputs
Attack Surface

FrenchMap Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[french-map] controllers\api_controller.php:8
WordPress Hooks 5
actioninitfrenchmap.php:80
actionadmin_initfrenchmap.php:81
actionadmin_initfrenchmap.php:82
actionadmin_menufrenchmap.php:83
actionadmin_enqueue_scriptsfrenchmap.php:84
Maintenance & Trust

FrenchMap Maintenance & Trust

Maintenance Signals

WordPress version tested6.4.8
Last updatedNov 10, 2023
PHP min version5.6.20
Downloads1K

Community Trust

Rating0/100
Number of ratings0
Active installs60
Developer Profile

FrenchMap Developer Profile

Wizard Widgets

2 plugins · 70 total installs

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

How We Detect FrenchMap

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/frenchmap/stylesheet.css/wp-content/plugins/frenchmap/js/frenchmap.js/wp-content/plugins/frenchmap/js/wp-color-picker-alpha.min.js/wp-content/plugins/frenchmap/js/wp-color-picker-init.js/wp-content/plugins/frenchmap/images/frenchmap_icon.svg/wp-content/plugins/frenchmap/images/frenchmap_logo.png
Script Paths
/wp-content/plugins/frenchmap/js/frenchmap.js/wp-content/plugins/frenchmap/js/wp-color-picker-alpha.min.js/wp-content/plugins/frenchmap/js/wp-color-picker-init.js
Version Parameters
frenchmap/stylesheet.css?ver=frenchmap/js/frenchmap.js?ver=

HTML / DOM Fingerprints

CSS Classes
frenchmap_application_windowfrenchmap_application_layoutfrenchmap_default_fontfrenchmap_main_titlefrenchmap_main_descriptionfrenchmap_error_boxfrenchmap_textboxfrenchmap-p-input
Data Attributes
id="frenchmap_application_window"id="frenchmap_application_layout"id="frenchmap_output_box"class="frenchmap_main_description"id="frenchmap_output_form_config"class="frenchmap_error_box"+2 more
Shortcode Output
<b>[french-map]</b>
FAQ

Frequently Asked Questions about FrenchMap