Plugin Output Cache Security & Risk Analysis

wordpress.org/plugins/plugin-output-cache

Plugin Output Cache can be used by other plugins to cache portions of their output for efficiency.

30 active installs v4.0.8 PHP + WP 1.5+ Updated Sep 23, 2008
cachepluginsspeed
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Plugin Output Cache Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 17yr ago
Risk Assessment

The plugin "plugin-output-cache" v4.0.8 exhibits a strong security posture in several key areas. The absence of known vulnerabilities (CVEs) and the fact that all identified SQL queries utilize prepared statements are significant strengths. Furthermore, the plugin has a remarkably small attack surface with no exposed AJAX handlers, REST API routes, shortcodes, or cron events that lack authorization checks. This indicates a good understanding of secure WordPress development practices regarding input sanitization and access control. The taint analysis also shows no critical or high-severity unsanitized flows, which is very positive.

However, a significant concern arises from the output escaping. With 10 total outputs analyzed and 0% properly escaped, this represents a substantial risk. Unescaped output is a primary vector for Cross-Site Scripting (XSS) vulnerabilities, allowing attackers to inject malicious scripts into the user's browser. While the current lack of historical vulnerabilities and a small attack surface are encouraging, the complete lack of output escaping is a critical flaw that cannot be overlooked. A balanced conclusion is that the plugin has a solid foundation in preventing common vulnerabilities like SQL injection and unauthorized access, but it suffers from a critical deficiency in output sanitization, making it susceptible to XSS attacks.

Key Concerns

  • Output escaping is completely missing
Vulnerabilities
None known

Plugin Output Cache Security Vulnerabilities

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

Plugin Output Cache Release Timeline

v4.0.8Current
v4.0.7
v4.0.6
v4.0.5
v4.0.0
Code Analysis
Analyzed Apr 16, 2026

Plugin Output Cache Code Analysis

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

SQL Query Safety

100% prepared4 total queries

Output Escaping

0% escaped10 total outputs
Attack Surface

Plugin Output Cache Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 12
actionadmin_menupoc-cache-admin.php:92
actionpublish_postpoc-cache.php:217
actionedit_postpoc-cache.php:218
actiondelete_postpoc-cache.php:219
actionpublish_phonepoc-cache.php:220
actiondelete_commentpoc-cache.php:221
actiontrackback_postpoc-cache.php:223
actionpingback_postpoc-cache.php:224
actioncomment_postpoc-cache.php:225
actionedit_commentpoc-cache.php:226
actionwp_set_comment_statuspoc-cache.php:227
actionplugins_loadedpoc-cache.php:233
Maintenance & Trust

Plugin Output Cache Maintenance & Trust

Maintenance Signals

WordPress version tested2.6.2
Last updatedSep 23, 2008
PHP min version
Downloads11K

Community Trust

Rating0/100
Number of ratings0
Active installs30
Developer Profile

Plugin Output Cache Developer Profile

RobMarsh

6 plugins · 2K total installs

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

How We Detect Plugin Output Cache

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/plugin-output-cache/poc-cache.php

HTML / DOM Fingerprints

HTML Comments
<!-- innards -->
JS Globals
POC_CACHEPOC_CACHE_4
FAQ

Frequently Asked Questions about Plugin Output Cache