Vulnerabilities (CVE)

Filtered by vendor Ays-pro Subscribe
Filtered by product Secure Copy Content Protection And Content Locking
Total 5 CVE
CVE Vendors Products Updated CVSS v2 CVSS v3
CVE-2024-6888 1 Ays-pro 1 Secure Copy Content Protection And Content Locking 2024-10-07 N/A 4.8 MEDIUM
The Secure Copy Content Protection and Content Locking WordPress plugin before 4.1.7 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup)
CVE-2024-6889 1 Ays-pro 1 Secure Copy Content Protection And Content Locking 2024-10-07 N/A 4.8 MEDIUM
The Secure Copy Content Protection and Content Locking WordPress plugin before 4.1.7 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup).
CVE-2024-6138 1 Ays-pro 1 Secure Copy Content Protection And Content Locking 2024-07-12 N/A 4.8 MEDIUM
The Secure Copy Content Protection and Content Locking WordPress plugin before 4.0.9 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup).
CVE-2021-24931 1 Ays-pro 1 Secure Copy Content Protection And Content Locking 2024-02-04 7.5 HIGH 9.8 CRITICAL
The Secure Copy Content Protection and Content Locking WordPress plugin before 2.8.2 does not escape the sccp_id parameter of the ays_sccp_results_export_file AJAX action (available to both unauthenticated and authenticated users) before using it in a SQL statement, leading to an SQL injection.
CVE-2021-24484 1 Ays-pro 1 Secure Copy Content Protection And Content Locking 2024-02-04 6.5 MEDIUM 7.2 HIGH
The get_reports() function in the Secure Copy Content Protection and Content Locking WordPress plugin before 2.6.7 did not use whitelist or validate the orderby parameter before using it in SQL statements passed to the get_results() DB calls, leading to SQL injection issues in the admin dashboard