Giornalismo Story Details Security & Risk Analysis

wordpress.org/plugins/giornalismo-story-details

Creates a custom write panel for use in the Giornalismo theme.

40 active installs v1.0.1 PHP + WP 4.0+ Updated Nov 14, 2017
custom-write-panelgiornalismo
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Giornalismo Story Details Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 8yr ago
Risk Assessment

The "giornalismo-story-details" plugin version 1.0.1 exhibits a strong security posture based on the provided static analysis. The absence of any AJAX handlers, REST API routes, shortcodes, or cron events means the attack surface is effectively zero, which is an excellent security practice. Furthermore, the code signals indicate a positive trend with all SQL queries using prepared statements and the presence of both nonce and capability checks, suggesting an awareness of fundamental WordPress security principles. There are no recorded vulnerabilities, including CVEs, which further bolsters its current safety.

However, a significant concern arises from the output escaping. With only 29% of 17 total outputs properly escaped, there is a substantial risk of Cross-Site Scripting (XSS) vulnerabilities. Unsanitized output can allow attackers to inject malicious scripts that could compromise user sessions or redirect users to malicious sites. While the plugin appears to be well-protected against common entry points and database manipulation, this specific weakness in output handling is a critical flaw that requires immediate attention.

In conclusion, the "giornalismo-story-details" plugin demonstrates good foundational security practices by minimizing its attack surface and securing its database interactions. The lack of vulnerability history is a positive indicator. Nevertheless, the severe lack of proper output escaping presents a considerable XSS risk that significantly overshadows these strengths. Addressing this output sanitization issue should be the top priority to mitigate potential security breaches.

Key Concerns

  • Insufficient output escaping (29%)
Vulnerabilities
None known

Giornalismo Story Details Security Vulnerabilities

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

Giornalismo Story Details Code Analysis

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

Output Escaping

29% escaped17 total outputs
Attack Surface

Giornalismo Story Details Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 2
actionadmin_menugiornalismo-story-details.php:19
actionsave_postgiornalismo-story-details.php:100
Maintenance & Trust

Giornalismo Story Details Maintenance & Trust

Maintenance Signals

WordPress version tested4.9.29
Last updatedNov 14, 2017
PHP min version
Downloads5K

Community Trust

Rating100/100
Number of ratings1
Active installs40
Developer Profile

Giornalismo Story Details Developer Profile

Jacob Martella

9 plugins · 230 total installs

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

How We Detect Giornalismo Story Details

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

Asset Fingerprints

HTML / DOM Fingerprints

CSS Classes
widefat
Data Attributes
name="giornalismo_photo_credit"id="giornalismo_photo_credit"name="giornalismo_photo_caption"id="giornalismo_photo_caption"name="giornalismo_featured_video"id="giornalismo_featured_video"+8 more
FAQ

Frequently Asked Questions about Giornalismo Story Details