Schedule Notice Security & Risk Analysis

wordpress.org/plugins/simple-schedule-notice

Just another schedule notice plugin. Simple but practical.

10 active installs v1.0.8 PHP + WP + Updated Unknown
mailnoticenotificationreminderschedule
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Schedule Notice Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs
Risk Assessment

The plugin 'simple-schedule-notice' v1.0.8 exhibits a generally good security posture based on the provided static analysis and vulnerability history. The absence of identified CVEs, dangerous functions, file operations, external HTTP requests, and the use of prepared statements for all SQL queries are all positive indicators. The plugin also appears to have a minimal attack surface with no exposed AJAX handlers, REST API routes, or shortcodes without proper authorization checks.

However, there are areas for concern. The low percentage of properly escaped output (5%) is a significant weakness. This suggests a high risk of Cross-Site Scripting (XSS) vulnerabilities, where malicious scripts could be injected and executed in the context of a user's browser. The taint analysis revealing two flows with unsanitized paths, even without critical or high severity, warrants attention as it indicates potential pathways for unintended data manipulation or access.

While the vulnerability history is clean, it's important to note that a lack of past vulnerabilities doesn't guarantee future security. The primary risks stem from the unescaped output and potential unsanitized data flows identified in the code analysis. Addressing these issues would significantly strengthen the plugin's security.

Key Concerns

  • Low output escaping percentage
  • Unsanitized paths found in taint analysis
Vulnerabilities
None known

Schedule Notice Security Vulnerabilities

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

Schedule Notice Code Analysis

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

Output Escaping

5% escaped20 total outputs
Data Flows
2 unsanitized

Data Flow Analysis

2 flows2 with unsanitized paths
simschntc_process_admin_page_request (simple-schedule-notice.php:97)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Schedule Notice Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 3
actionadmin_menusimple-schedule-notice.php:24
actionadmin_enqueue_scriptssimple-schedule-notice.php:25
filterprivate_title_formatsimple-schedule-notice.php:38
Maintenance & Trust

Schedule Notice Maintenance & Trust

Maintenance Signals

WordPress version tested5.7.15
Last updatedUnknown
PHP min version
Downloads2K

Community Trust

Rating80/100
Number of ratings1
Active installs10
Developer Profile

Schedule Notice Developer Profile

Eiichiro Kamiya

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 Schedule Notice

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/simple-schedule-notice/simple-schedule-notice.css/wp-content/plugins/simple-schedule-notice/simple-schedule-notice.js
Script Paths
/wp-content/plugins/simple-schedule-notice/simple-schedule-notice.js
Version Parameters
simple-schedule-notice.css?ver=simple-schedule-notice.js?ver=

HTML / DOM Fingerprints

CSS Classes
shdntc-admblockshdntc-fldsetshdntc-remarksshdntc-errors
Data Attributes
data-imdata-ph
FAQ

Frequently Asked Questions about Schedule Notice