
GNU Terry Pratchett Security & Risk Analysis
wordpress.org/plugins/gnu-terry-pratchettAdd an X-Clacks-Overhead header with “GNU Terry Pratchett” to all non-admin pages.
Is GNU Terry Pratchett Safe to Use in 2026?
Generally Safe
Score 100/100GNU Terry Pratchett has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.
The "gnu-terry-pratchett" plugin version 0.4.1 exhibits a strong security posture based on the static analysis. The absence of any identified AJAX handlers, REST API routes, shortcodes, or cron events significantly limits the plugin's attack surface. Furthermore, the code shows adherence to good security practices by not using dangerous functions, performing file operations, or making external HTTP requests. The SQL queries are all prepared, and while there are some output operations, the majority are properly escaped, indicating a good effort to prevent XSS vulnerabilities. The lack of any registered vulnerabilities in its history is also a positive indicator.
However, the static analysis did reveal some areas for improvement. The complete absence of nonce checks and capability checks is a notable concern. While the attack surface is currently zero, if any entry points were to be introduced in the future without proper authentication or authorization checks, it could lead to significant security risks. The 20% of outputs that are not properly escaped, while not a critical flaw in isolation, still represent a potential vector for cross-site scripting (XSS) vulnerabilities, especially as the plugin evolves and potentially gains more functionality. The current lack of taint analysis results is also inconclusive; it might indicate a small code base or the absence of complex data flows, but it doesn't definitively confirm the absence of all taint-related issues.
In conclusion, the "gnu-terry-pratchett" plugin currently appears to be a low-risk plugin due to its minimal attack surface and adherence to some best practices like prepared SQL statements. The main weaknesses lie in the complete absence of nonces and capability checks, which could become critical if new features are added. The unescaped outputs, while not a critical finding, should be addressed to ensure a more robust security profile. The plugin's history of zero vulnerabilities is encouraging, but continuous vigilance and addressing the identified gaps are essential for long-term security.
Key Concerns
- Missing nonce checks
- Missing capability checks
- Unescaped output present (20%)
GNU Terry Pratchett Security Vulnerabilities
GNU Terry Pratchett Code Analysis
Output Escaping
GNU Terry Pratchett Attack Surface
WordPress Hooks 4
Maintenance & Trust
GNU Terry Pratchett Maintenance & Trust
Maintenance Signals
Community Trust
GNU Terry Pratchett Alternatives
HTTP Headers
http-headers
HTTP Headers adds CORS & security HTTP headers to your website.
Simple Iframe Buster
simple-iframe-buster
Provides a method of setting the X-Frame-Options header to SAMEORIGIN. Also enqueues a javascript based iframe blocker.
WP Secure HTTP Headers
wp-secure-http-headers
License: GPLv2 or later WordPress plugin to add secure headers to your website.
Eazy HTTP Headers
eazy-http-headers
Provides settings to activate three HTTP header settings for X-Frame-Options, X-XSS Protection & X-Content-Type-Options.
SeaSP Community Edition
sea-sp-community-edition
SeaSP Community Edition is an automated Content Security Policy Manager. SeaSP allows you to create, configure, manage, and deploy a Content Security …
GNU Terry Pratchett Developer Profile
1 plugin · 1K total installs
How We Detect GNU Terry Pratchett
Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.
Asset Fingerprints
HTML / DOM Fingerprints
http-equiv="X-Clacks-Overhead"