SOWPROG Events Security & Risk Analysis

wordpress.org/plugins/sowprog-events

Displays Sowprog events

10 active installs v0.5 PHP + WP 3.4+ Updated May 24, 2020
eventssowprog
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is SOWPROG Events Safe to Use in 2026?

Generally Safe

Score 85/100

SOWPROG Events 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 sowprog-events plugin version 0.5 exhibits a mixed security posture. On the positive side, it demonstrates good practices by utilizing prepared statements for all SQL queries and has no known historical vulnerabilities. The attack surface is also relatively small, with a single shortcode as the only identified entry point, and importantly, no unauthenticated entry points were found in the static analysis.

However, several significant concerns are present. The most glaring issue is the extremely low percentage of properly escaped output (15%), indicating a high risk of Cross-Site Scripting (XSS) vulnerabilities. While the static analysis did not identify critical or high severity taint flows, the presence of two flows with unsanitized paths, coupled with poor output escaping, strongly suggests that malicious scripts could be injected and executed. Furthermore, the complete absence of nonce checks and capability checks on its entry points (even though the attack surface is small) is a notable weakness. The plugin also performs file operations and external HTTP requests without clear sanitization or validation mechanisms indicated in the provided data, which could be potential vectors for attack if not handled carefully.

In conclusion, while the plugin benefits from a clean vulnerability history and secure SQL practices, the pervasive lack of output escaping and the absence of essential security checks like nonces and capability checks on its entry points represent substantial security risks. The taint analysis, despite not flagging critical issues, combined with the poor output escaping, warrants significant caution.

Key Concerns

  • Low percentage of properly escaped output
  • Unsanitized paths in taint flows
  • No nonce checks on entry points
  • No capability checks on entry points
Vulnerabilities
None known

SOWPROG Events Security Vulnerabilities

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

SOWPROG Events Release Timeline

v0.5Current
v0.4
v0.3
v0.2
v0.1
Code Analysis
Analyzed Mar 17, 2026

SOWPROG Events Code Analysis

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

Output Escaping

15% escaped39 total outputs
Data Flows · Security
2 unsanitized

Data Flow Analysis

2 flows2 with unsanitized paths
form (sowprog_events_configuration.php:163)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

SOWPROG Events Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[sp_events_private] sowprog_events_virtual_page.php:159
WordPress Hooks 5
actionadmin_menusowprog_events_configuration.php:236
filterthe_postssowprog_events_virtual_page.php:27
actionwp_titlesowprog_events_virtual_page.php:151
actioninitsowprog_events_virtual_page.php:153
actionwidgets_initsowprog_events_widget.php:108
Maintenance & Trust

SOWPROG Events Maintenance & Trust

Maintenance Signals

WordPress version tested5.4.19
Last updatedMay 24, 2020
PHP min version
Downloads2K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

SOWPROG Events Developer Profile

A31V

2 plugins · 20 total installs

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

How We Detect SOWPROG Events

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/sowprog-events/includes/js/pickadate.js-3.5.5/lib/picker.js/wp-content/plugins/sowprog-events/includes/js/pickadate.js-3.5.5/lib/picker.date.js/wp-content/plugins/sowprog-events/includes/js/pickadate.js-3.5.5/lib/picker.time.js/wp-content/plugins/sowprog-events/includes/js/pickadate.js-3.5.5/lib/translations/fr_FR.js/wp-content/plugins/sowprog-events/includes/js/pickadate.js-3.5.5/lib/legacy.js/wp-content/plugins/sowprog-events/includes/js/sowprog_events.js/wp-content/plugins/sowprog-events/includes/js/pickadate.js-3.5.5/lib/themes/classic.css/wp-content/plugins/sowprog-events/includes/js/pickadate.js-3.5.5/lib/themes/classic.date.css+3 more
Script Paths
/wp-content/plugins/sowprog-events/includes/js/sowprog_events.js/wp-content/plugins/sowprog-events/includes/js/sowprog_events_widget.js

HTML / DOM Fingerprints

CSS Classes
icon-search
Data Attributes
id="swc_date"name="swc_date"id="swc_query"name="swc_query"id="swc_events_small_div"
JS Globals
sowprog_events_widget_parameters
REST Endpoints
/v1/widget/oembed/basic/events//v1/widget/oembed/basic/locations/
FAQ

Frequently Asked Questions about SOWPROG Events