TheRich WP Fullcalendar Security & Risk Analysis

wordpress.org/plugins/therich-wp-fullcalendar

TheRich WP Fullcalendar helps you to add events and show thoes events in fullcalendar.

10 active installs v1.0.0 PHP + WP 4.0+ Updated Jun 15, 2019
add-events-fullcalendareventcalendarfullcalendarwordpressfullcalendar
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is TheRich WP Fullcalendar Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 6yr ago
Risk Assessment

The therich-wp-fullcalendar v1.0.0 plugin exhibits a generally good security posture based on the provided static analysis. It has a minimal attack surface with only one shortcode and no unprotected entry points. The code demonstrates strong adherence to security best practices by utilizing prepared statements for all SQL queries, performing necessary nonce and capability checks, and avoiding dangerous functions, file operations, and external HTTP requests. The absence of any recorded vulnerabilities, including CVEs, further reinforces this positive assessment.

However, there is a slight concern regarding output escaping, where 33% of the outputs are not properly escaped. While not critical in isolation given the lack of other exploitable entry points, this could potentially lead to cross-site scripting (XSS) vulnerabilities if malicious data were to be introduced through the shortcode and then displayed without proper sanitization. The lack of taint analysis results is also a neutral factor, as it doesn't indicate the presence of issues but also doesn't confirm their absence. Overall, the plugin is well-developed from a security perspective, with the primary area for improvement being the consistent and complete escaping of all output.

In conclusion, therich-wp-fullcalendar v1.0.0 is a relatively secure plugin due to its limited attack surface, robust authentication checks, and safe coding practices for database interactions. The absence of known vulnerabilities is a significant strength. The main weakness lies in the incomplete output escaping, which, while not immediately exploitable with the current configuration, represents a potential risk that should be addressed for maximum security.

Key Concerns

  • Unescaped output found
Vulnerabilities
None known

TheRich WP Fullcalendar Security Vulnerabilities

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

TheRich WP Fullcalendar Code Analysis

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

Output Escaping

67% escaped6 total outputs
Attack Surface

TheRich WP Fullcalendar Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[TheRicHWordpressFullcalendar] therichwordpressfullcalender.php:173
WordPress Hooks 5
actioninittherichwordpressfullcalender.php:17
actionwp_enqueue_scriptstherichwordpressfullcalender.php:89
actionadmin_enqueue_scriptstherichwordpressfullcalender.php:101
actionadd_meta_boxestherichwordpressfullcalender.php:177
actionsave_posttherichwordpressfullcalender.php:208
Maintenance & Trust

TheRich WP Fullcalendar Maintenance & Trust

Maintenance Signals

WordPress version tested5.2.24
Last updatedJun 15, 2019
PHP min version
Downloads1K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

TheRich WP Fullcalendar Developer Profile

Ajay Malhotra

2 plugins · 20 total installs

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

How We Detect TheRich WP Fullcalendar

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/therich-wp-fullcalendar/dist/bootstrap.min.js/wp-content/plugins/therich-wp-fullcalendar/dist/moment.min.js/wp-content/plugins/therich-wp-fullcalendar/dist/fullCalendar.js/wp-content/plugins/therich-wp-fullcalendar/dist/bootstrap.min.css/wp-content/plugins/therich-wp-fullcalendar/dist/fullcalendar.min.css/wp-content/plugins/therich-wp-fullcalendar/dist/jquery-ui.js/wp-content/plugins/therich-wp-fullcalendar/dist/jquery-ui.css
Script Paths
/wp-content/plugins/therich-wp-fullcalendar/dist/bootstrap.min.js/wp-content/plugins/therich-wp-fullcalendar/dist/moment.min.js/wp-content/plugins/therich-wp-fullcalendar/dist/fullCalendar.js/wp-content/plugins/therich-wp-fullcalendar/dist/jquery-ui.js
Version Parameters
therich-wp-fullcalendar/dist/bootstrap.min.js?ver=therich-wp-fullcalendar/dist/moment.min.js?ver=therich-wp-fullcalendar/dist/fullCalendar.js?ver=therich-wp-fullcalendar/dist/bootstrap.min.css?ver=therich-wp-fullcalendar/dist/fullcalendar.min.css?ver=therich-wp-fullcalendar/dist/jquery-ui.js?ver=therich-wp-fullcalendar/dist/jquery-ui.css?ver=

HTML / DOM Fingerprints

CSS Classes
calendardiveventdetail
Data Attributes
id="datepickerstart"id="datepickerend"name="my_meta_box_event_start"name="my_meta_box_event_end"
JS Globals
moment$
Shortcode Output
[TheRicHWordpressFullcalendar]
FAQ

Frequently Asked Questions about TheRich WP Fullcalendar