Tempus Security & Risk Analysis

wordpress.org/plugins/tempus

Only in Portuguese (BR) yet. Others languages soon. Este plugin tem como objetivo manter um controle simples e eficiente de eventos

10 active installs v0.1 PHP + WP 2.0+ Updated Unknown
calendardiaryeventstaskstempus
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Tempus Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs
Risk Assessment

The "tempus" plugin v0.1 exhibits a mixed security posture. While the static analysis reports no dangerous functions, no file operations, and no external HTTP requests, and the vulnerability history is clean, several critical concerns are present. A significant weakness is the complete lack of output escaping for all 17 identified outputs. This, combined with three taint analysis flows with unsanitized paths, creates a high risk for cross-site scripting (XSS) vulnerabilities. The absence of nonce checks and capability checks, especially on the single shortcode entry point, further amplifies this risk, as these are fundamental WordPress security mechanisms for preventing unauthorized actions and ensuring data integrity. The clean vulnerability history is positive, suggesting the plugin might be new or has not yet been extensively analyzed, but the current code analysis reveals clear and present dangers.

Key Concerns

  • Unescaped output for all identified outputs
  • Taint flows with unsanitized paths (critical severity)
  • No nonce checks
  • No capability checks
Vulnerabilities
None known

Tempus Security Vulnerabilities

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

Tempus Code Analysis

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

SQL Query Safety

100% prepared8 total queries

Output Escaping

0% escaped17 total outputs
Data Flows
3 unsanitized

Data Flow Analysis

3 flows3 with unsanitized paths
tempus_edit_event_page (admin.php:103)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Tempus Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[list-events] tempus.php:139
WordPress Hooks 4
actionadmin_menuadmin.php:304
actionadmin_print_scriptsadmin.php:320
actionadmin_print_stylesadmin.php:321
actioninittempus.php:142
Maintenance & Trust

Tempus Maintenance & Trust

Maintenance Signals

WordPress version tested3.9.40
Last updatedUnknown
PHP min version
Downloads4K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Tempus Developer Profile

patrixsbs

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 Tempus

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

Asset Fingerprints

HTML / DOM Fingerprints

CSS Classes
tempustempus-eventstempus-event
Data Attributes
id="title"name="title"id="description"name="description"id="start-time"name="start-time"+9 more
Shortcode Output
[list-events]
FAQ

Frequently Asked Questions about Tempus