Right Click Ban – Content Protection Security & Risk Analysis

wordpress.org/plugins/right-click-disable-or-ban

Protect content by disabling F12, developer tools & right click context menu to prevent text copying, image dragging, and unauthorized access.

100 active installs v2.1.0 PHP 7.4+ WP 5.0+ Updated Mar 27, 2026
content-protectioncopy-protectiondisable-right-clickimage-protectionright-click-disable
99
A · Safe
CVEs total1
Unpatched0
Last CVEApr 16, 2025
Safety Verdict

Is Right Click Ban – Content Protection Safe to Use in 2026?

Generally Safe

Score 99/100

Right Click Ban – Content Protection has a strong security track record. Known vulnerabilities have been patched promptly. It's a solid choice for most WordPress installations.

1 known CVELast CVE: Apr 16, 2025Updated 1mo ago
Risk Assessment

The "right-click-disable-or-ban" plugin v2.0.1 exhibits a generally strong security posture, with a significant portion of its code adhering to best practices. The static analysis reveals a small attack surface with no unprotected entry points, and excellent adherence to prepared statements for SQL queries (93%) and output escaping (96%). The presence of nonce and capability checks further bolsters its security. However, the taint analysis identifies two flows with unsanitized paths, both flagged as high severity. While these don't appear to be directly exploitable given the absence of critical or high vulnerabilities and the plugin's limited functionality, they represent a potential concern if not properly addressed or if the plugin's scope expands.

The vulnerability history shows a single medium-severity CVE in the past, which is now patched. This indicates that while vulnerabilities can occur, they have been addressed. The common vulnerability type being CSRF suggests that input validation and nonce checks have been areas requiring attention in the past. Overall, the plugin demonstrates good security practices, but the identified taint flows warrant attention to ensure no hidden risks exist.

Key Concerns

  • High severity unsanitized taint flows detected
  • Previous medium CVE indicates potential past weaknesses
Vulnerabilities
1 published

Right Click Ban – Content Protection Security Vulnerabilities

CVEs by Year

1 CVE in 2025
2025
Patched Has unpatched

Severity Breakdown

Medium
1

1 total CVE

CVE-2025-39548medium · 6.1Cross-Site Request Forgery (CSRF)

Right Click Disable OR Ban <= 1.1.17 - Cross-Site Request Forgery to Stored Cross-Site Scripting

Apr 16, 2025 Patched in 1.2.0 (6d)
Version History

Right Click Ban – Content Protection Release Timeline

v2.1.0Current
v2.0.1
v2.0.0
v1.2.3
v1.2.2
v1.2.1
v1.2.0
v1.1.171 CVE
v1.1.161 CVE
v1.1.151 CVE
v1.1.141 CVE
v1.1.131 CVE
v1.1.121 CVE
v1.1.111 CVE
v1.1.101 CVE
v1.1.91 CVE
v1.1.81 CVE
v1.1.71 CVE
v1.1.61 CVE
v1.1.51 CVE
Code Analysis
Analyzed Mar 16, 2026

Right Click Ban – Content Protection Code Analysis

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

SQL Query Safety

93% prepared14 total queries

Output Escaping

96% escaped25 total outputs
Data Flows · Security
2 unsanitized

Data Flow Analysis

2 flows2 with unsanitized paths
log_event (includes\class-ajax-handler.php:69)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Right Click Ban – Content Protection Attack Surface

Entry Points3
Unprotected0

AJAX Handlers 3

authwp_ajax_rcb_save_settingsincludes\class-ajax-handler.php:24
authwp_ajax_rcb_log_eventincludes\class-ajax-handler.php:27
noprivwp_ajax_rcb_log_eventincludes\class-ajax-handler.php:28
WordPress Hooks 2
actionadmin_menuright-click-disable-or-ban.php:56
actionwp_enqueue_scriptsright-click-disable-or-ban.php:59
Maintenance & Trust

Right Click Ban – Content Protection Maintenance & Trust

Maintenance Signals

WordPress version tested6.9.4
Last updatedMar 27, 2026
PHP min version7.4
Downloads23K

Community Trust

Rating50/100
Number of ratings2
Active installs100
Developer Profile

Right Click Ban – Content Protection Developer Profile

A WP Life

65 plugins · 90K total installs

77
trust score
Avg Security Score
97/100
Avg Patch Time
266 days
View full developer profile
Detection Fingerprints

How We Detect Right Click Ban – Content Protection

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/right-click-disable-or-ban/admin/css/rcb-admin.css/wp-content/plugins/right-click-disable-or-ban/assets/css/rcb-frontend.css/wp-content/plugins/right-click-disable-or-ban/assets/js/rcb-frontend.js
Script Paths
/wp-content/plugins/right-click-disable-or-ban/assets/js/rcb-frontend.js
Version Parameters
right-click-disable-or-ban/admin/css/rcb-admin.css?ver=right-click-disable-or-ban/assets/css/rcb-frontend.css?ver=right-click-disable-or-ban/assets/js/rcb-frontend.js?ver=

HTML / DOM Fingerprints

CSS Classes
rcb-page-headerrcb-header-iconrcb-header-contentrcb-page-titlercb-page-subtitlercb-page-versionrcb-cardrcb-card-header+2 more
Data Attributes
data-rcb-disable-rightclickdata-rcb-disable-selectiondata-rcb-disable-dragdata-rcb-ban-messagedata-rcb-ban-message-imgdata-rcb-ban-message-selection
JS Globals
RCB_PLUGIN_VERRCB_PLUGIN_URL
FAQ

Frequently Asked Questions about Right Click Ban – Content Protection