Append or Prepend Content Security & Risk Analysis

wordpress.org/plugins/append-or-prepend-content

Add content before or after every post, page or Custom Post Type.

80 active installs v2.1.0 PHP 7.3+ WP 5.7+ Updated Mar 23, 2022
contentcustom-post-typeposts
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Append or Prepend Content Safe to Use in 2026?

Generally Safe

Score 85/100

Append or Prepend Content has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 4yr ago
Risk Assessment

Based on the provided static analysis and vulnerability history, the 'append-or-prepend-content' plugin v2.1.0 exhibits a strong security posture. The code analysis reveals no detected dangerous functions, no raw SQL queries, and all output is properly escaped. There are no file operations or external HTTP requests, and importantly, no identified taint flows that indicate potential vulnerabilities. This indicates a proactive approach to secure coding practices within the plugin.

The plugin's attack surface is reported as zero, meaning there are no exposed AJAX handlers, REST API routes, shortcodes, or cron events. Furthermore, the vulnerability history shows no recorded CVEs of any severity, which is a very positive sign. This absence of past vulnerabilities suggests a well-maintained and security-conscious development process.

While the current analysis presents a very favorable security picture, it's worth noting the complete absence of nonce and capability checks. Although this might be justified if the plugin has no user-facing interactive features that require protection, it's a common area for security weaknesses in WordPress plugins. The overall conclusion is that this version of the plugin appears to be highly secure according to the provided data, with no immediate risks identified.

Vulnerabilities
None known

Append or Prepend Content Security Vulnerabilities

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

Append or Prepend Content Code Analysis

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

Output Escaping

100% escaped5 total outputs
Attack Surface

Append or Prepend Content Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 11
actionplugins_loadedapp-prep-content.php:34
actionadmin_initapp-prep-content.php:46
actionadmin_initinc\admin.php:14
actionadmin_menuinc\admin.php:15
actionplugin_row_metainc\admin.php:16
filterthe_contentinc\content.php:19
filterthe_contentinc\content.php:94
actionenqueue_block_editor_assetsinc\editor.php:14
actioninitinc\meta.php:20
actioninitinc\post-type.php:16
filterthe_titleinc\post-type.php:17
Maintenance & Trust

Append or Prepend Content Maintenance & Trust

Maintenance Signals

WordPress version tested5.9.13
Last updatedMar 23, 2022
PHP min version7.3
Downloads10K

Community Trust

Rating100/100
Number of ratings2
Active installs80
Developer Profile

Append or Prepend Content Developer Profile

Ignacio Cruz Moreno

4 plugins · 170 total installs

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

How We Detect Append or Prepend Content

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/append-or-prepend-content/build/index.asset.php/wp-content/plugins/append-or-prepend-content/build/index.js
Script Paths
/wp-content/plugins/append-or-prepend-content/build/index.js
Version Parameters
append-or-prepend-content/build/index.asset.phpappend-or-prepend-content/build/index.js

HTML / DOM Fingerprints

JS Globals
window.appOrPrepend
REST Endpoints
/wp-json/wp/v2/apporprep_content
FAQ

Frequently Asked Questions about Append or Prepend Content