Push Monetization Security & Risk Analysis

wordpress.org/plugins/neptuneads-monetization

Earn money with NeptuneAds Push!

0 active installs v20181101 PHP + WP + Updated Dec 14, 2018
adsmonetizationprofitpushrevenue
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Push Monetization Safe to Use in 2026?

Generally Safe

Score 85/100

Push Monetization 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 neptuneads-monetization plugin v20181101 exhibits a generally good security posture based on the static analysis, with no exposed attack surface points and a complete absence of recorded vulnerabilities.

The code analysis reveals a cautious approach to sensitive operations, with all SQL queries utilizing prepared statements. However, a significant concern is the output escaping, where only 57% of outputs are properly escaped. This leaves a potential for cross-site scripting (XSS) vulnerabilities if user-supplied data is not handled meticulously throughout the remaining unescaped outputs.

The lack of any known CVEs or historical vulnerabilities is a strong positive indicator. This suggests that either the plugin has been well-maintained and secured from its inception, or that it has not been a target of widespread vulnerability discovery. Despite the positive history, the identified weakness in output escaping warrants attention to ensure that no new vulnerabilities are introduced or remain undiscovered.

Key Concerns

  • Insufficient output escaping
Vulnerabilities
None known

Push Monetization Security Vulnerabilities

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

Push Monetization Release Timeline

No version history available.
Code Analysis
Analyzed Mar 17, 2026

Push Monetization Code Analysis

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

Output Escaping

57% escaped7 total outputs
Attack Surface

Push Monetization Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 4
actionpre_get_postsneptune-monetization.php:47
actionadmin_menuneptune-monetization.php:51
actionadmin_initneptune-monetization.php:52
actionwp_enqueue_scriptsneptune-monetization.php:115
Maintenance & Trust

Push Monetization Maintenance & Trust

Maintenance Signals

WordPress version tested
Last updatedDec 14, 2018
PHP min version
Downloads1K

Community Trust

Rating0/100
Number of ratings0
Active installs0
Developer Profile

Push Monetization Developer Profile

neptuneads

1 plugin · 0 total installs

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

How We Detect Push Monetization

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/neptuneads-monetization/inc/manifest.json/wp-content/plugins/neptuneads-monetization/inc/service_worker.js
Script Paths
https://pushrev.karconsulting.us/tracker-wp.jshttps://pushrev.karconsulting.us/push-overlay.js
Version Parameters
neptuneads-monetization-push/tracker-wp.js?aff_id=neptuneads-monetization-push-overlay-css/push-overlay.cssneptuneads-monetization-push-overlay/push-overlay.js?text=

HTML / DOM Fingerprints

Data Attributes
name="neptune_affiliate_id"name="neptune_push_overlay"name="neptune_push_overlay_text"
JS Globals
window.neptune_affiliate_idwindow.neptune_push_overlaywindow.neptune_push_overlay_text
FAQ

Frequently Asked Questions about Push Monetization