I Agree! Popups Security & Risk Analysis

wordpress.org/plugins/i-agree-popups

Create T&C and disclaimer popups for use across your entire WordPress site or on individual posts and pages.

600 active installs v1.0 PHP + WP 3.8+ Updated May 5, 2016
disclaimermodalpopoverpopupwindow
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is I Agree! Popups Safe to Use in 2026?

Generally Safe

Score 85/100

I Agree! Popups has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 9yr ago
Risk Assessment

The 'i-agree-popups' v1.0 plugin exhibits a generally good security posture based on the provided static analysis. The absence of known vulnerabilities and CVEs is a strong positive indicator. Furthermore, the plugin demonstrates good practices by utilizing prepared statements for all SQL queries, employing nonce checks, and incorporating capability checks, suggesting an awareness of common WordPress security pitfalls. The zero-count for critical taint flows and unsanitized paths in the taint analysis also suggests that data is being handled with a reasonable degree of care.

However, a significant concern arises from the output escaping. With 42 total outputs and only 31% properly escaped, there is a substantial risk of Cross-Site Scripting (XSS) vulnerabilities. This means that user-supplied or otherwise dynamic data displayed within the plugin's interface is likely not being sufficiently sanitized, leaving it open to malicious script injection. While the attack surface appears minimal in terms of entry points, the lack of robust output escaping represents a tangible security weakness that could be exploited.

In conclusion, 'i-agree-popups' v1.0 benefits from a clean vulnerability history and good practices in data handling and authentication. Nevertheless, the pervasive issue with output escaping presents a notable risk. If the plugin is intended for public release or handles any user-configurable content, addressing the output escaping concerns should be a high priority to mitigate potential XSS attacks.

Key Concerns

  • Significant portion of output not properly escaped
Vulnerabilities
None known

I Agree! Popups Security Vulnerabilities

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

I Agree! Popups Code Analysis

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

Output Escaping

31% escaped42 total outputs
Attack Surface

I Agree! Popups Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 16
actiondashboard_glance_itemsincludes\i-agree-admin.php:29
actionadmin_headincludes\i-agree-admin.php:30
actionwp_enqueue_scriptsincludes\i-agree-enqueue.php:21
actiondashboard_glance_itemsincludes\i-agree-glancer.php:40
actionadd_meta_boxesincludes\i-agree-popup-metaboxes.php:21
actionsave_postincludes\i-agree-popup-metaboxes.php:22
actionadd_meta_boxesincludes\i-agree-popup-metaboxes.php:23
actionsave_postincludes\i-agree-popup-metaboxes.php:24
actionadd_meta_boxesincludes\i-agree-post-metaboxes.php:24
actionsave_postincludes\i-agree-post-metaboxes.php:25
actioninitincludes\i-agree-registration.php:23
filterpost_updated_messagesincludes\i-agree-registration.php:24
filterpost_row_actionsincludes\i-agree-registration.php:25
actionwp_footerincludes\i-agree-wp-footer.php:21
actionadmin_bar_menuincludes\i-agree-wp-footer.php:22
actioninitincludes\i-agree.php:21
Maintenance & Trust

I Agree! Popups Maintenance & Trust

Maintenance Signals

WordPress version tested4.5.33
Last updatedMay 5, 2016
PHP min version
Downloads11K

Community Trust

Rating88/100
Number of ratings5
Active installs600
Developer Profile

I Agree! Popups Developer Profile

Talisman

1 plugin · 600 total installs

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

How We Detect I Agree! Popups

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/i-agree-popups/assets/css/i-agree-popups.css

HTML / DOM Fingerprints

CSS Classes
iAgreePopuppopupBGpopupContainerpopupContentpopupChoicesyesNopopupChoiceButtonagree+1 more
HTML Comments
<!-- I Agree! Popups - http://www.talismansolutions.co.uk/i-agree-popups -->
Data Attributes
data-popup-id
JS Globals
rememberMe
FAQ

Frequently Asked Questions about I Agree! Popups