Content Upgrade Security & Risk Analysis

wordpress.org/plugins/content-upgrade

Note: Please refer the screenshot images to understand the complete working of the content upgrade plugin.

10 active installs v1.0.5 PHP + WP 4.5+ Updated Jan 23, 2019
content-lockcontent-lockercontent-upgradedownload-contentlead-generation
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Content Upgrade Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 7yr ago
Risk Assessment

The 'content-upgrade' plugin v1.0.5 presents a concerning security posture primarily due to a significant number of unprotected AJAX handlers. While the plugin demonstrates good practices in other areas, such as a high percentage of SQL queries using prepared statements and a majority of outputs being properly escaped, the lack of authentication checks on 10 out of 10 AJAX entry points creates a substantial attack surface. The taint analysis did reveal one flow with unsanitized paths, which, while not classified as critical or high severity in this instance, highlights a potential area for exploitation if inputs are not rigorously validated. The complete absence of recorded vulnerabilities, CVEs, or common vulnerability types in its history is a positive indicator, suggesting a history of relatively secure development or limited exposure. However, this lack of historical issues should not overshadow the immediate risks posed by the exposed AJAX endpoints. The plugin's strengths lie in its cautious approach to database operations and output handling, but its weakness in securing critical entry points requires immediate attention to mitigate potential unauthorized actions.

Key Concerns

  • AJAX handlers without authentication checks
  • Flows with unsanitized paths identified
  • File operations present
  • External HTTP requests present
  • Nonce checks partially implemented
  • Capability checks partially implemented
Vulnerabilities
None known

Content Upgrade Security Vulnerabilities

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

Content Upgrade Release Timeline

v1.0.5Current
v1.0.4
v1.0.3
v1.0.2
v1.0
Code Analysis
Analyzed Mar 16, 2026

Content Upgrade Code Analysis

Dangerous Functions
0
Raw SQL Queries
1
5 prepared
Unescaped Output
15
42 escaped
Nonce Checks
3
Capability Checks
3
File Operations
4
External Requests
8
Bundled Libraries
1

Bundled Libraries

TinyMCE

SQL Query Safety

83% prepared6 total queries

Output Escaping

74% escaped57 total outputs
Data Flows · Security
1 unsanitized

Data Flow Analysis

1 flows1 with unsanitized paths
<dlv_shortcode> (dlv_shortcode.php:0)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface
10 unprotected

Content Upgrade Attack Surface

Entry Points11
Unprotected10

AJAX Handlers 10

authwp_ajax_dlv_ajaxdlv_shortcode.php:104
noprivwp_ajax_dlv_ajaxdlv_shortcode.php:105
authwp_ajax_dlv_email_ajaxdlv_shortcode.php:107
noprivwp_ajax_dlv_email_ajaxdlv_shortcode.php:108
authwp_ajax_dlv_counterdlv_shortcode.php:110
noprivwp_ajax_dlv_counterdlv_shortcode.php:111
authwp_ajax_dlv_counterversion1.0\Dlv_1Point_Zero.php:21
noprivwp_ajax_dlv_counterversion1.0\Dlv_1Point_Zero.php:22
authwp_ajax_dlv_socialcounterversion1.0.0\Dlv_1Point_ZeroOne.php:23
noprivwp_ajax_dlv_socialcounterversion1.0.0\Dlv_1Point_ZeroOne.php:24

Shortcodes 1

[dlv] dlv_shortcode.php:72
WordPress Hooks 13
actionadmin_menudlv_shortcode.php:73
actionwp_enqueue_scriptsdlv_shortcode.php:74
actionwp_enqueue_scriptsdlv_shortcode.php:75
actionadmin_initdlv_shortcode.php:76
actionadmin_initdlv_shortcode.php:77
filterwp_mail_content_typedlv_shortcode.php:305
filtermce_external_pluginsdlv_shortcode.php:414
filtermce_buttonsdlv_shortcode.php:415
actionadmin_menudlv_shortcode.php:702
actiondlv_ajax_callbackversion1.0\Dlv_1Point_Zero.php:14
actiondlv_jsversion1.0\Dlv_1Point_Zero.php:15
actiondlv_ajaxversion1.0\Dlv_1Point_Zero.php:16
actiondlv_social_shortcodeversion1.0.0\Dlv_1Point_ZeroOne.php:22
Maintenance & Trust

Content Upgrade Maintenance & Trust

Maintenance Signals

WordPress version tested5.0.25
Last updatedJan 23, 2019
PHP min version
Downloads2K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Content Upgrade Developer Profile

pabbly

1 plugin · 10 total installs

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

How We Detect Content Upgrade

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/content-upgrade/css/content-upgrade.css/wp-content/plugins/content-upgrade/css/animate.css/wp-content/plugins/content-upgrade/css/dlv_custom.css/wp-content/plugins/content-upgrade/js/dlv_custom.js
Script Paths
/wp-content/plugins/content-upgrade/js/dlv_custom.js
Version Parameters
content-upgrade/css/content-upgrade.css?ver=content-upgrade/css/animate.css?ver=content-upgrade/css/dlv_custom.css?ver=content-upgrade/js/dlv_custom.js?ver=

HTML / DOM Fingerprints

CSS Classes
con_upg_wrap
HTML Comments
<!-- Start of Download Button --><!-- End of Download Button --><!-- Content Upgrade shortcode -->
Data Attributes
data-iddata-downloaddata-namedata-email
JS Globals
dlv_custom_obj
Shortcode Output
<a href="javascript:void(0);" class="btn btn-primary btn-lg download-button dlv_button_class" data-id=
FAQ

Frequently Asked Questions about Content Upgrade