HomeWordPress vulnerabilitiesSecure Copy Content Protection and Content Locking
Secure Copy Content Protection and Content Locking vulnerabilities
Secure Copy Content Protection and Content Locking has 10 known vulnerabilities in this database. The most recent published record is dated 12 Jun 2026.
- Known vulnerabilities
- 10
- Active installs
- 20,000+
- Latest version
- 5.2.9
- Last updated
- 29 Sep 2026
- Most recent
- 12 Jun 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-9269 | Low 3.5 | Before 5.1.5 | Fixed in 5.1.5 | 12 Jun 2026 |
| Cross-site scripting (XSS) CVE-2026-2367 | Medium 6.4 | Up to 5.0.1 | Fixed in a later version (latest 5.2.9) | 25 Feb 2026 |
| Cross-site scripting (XSS) CVE-2026-1320 | High 7.2 | Up to 4.9.8 | Fixed in a later version (latest 5.2.9) | 12 Feb 2026 |
| Cross-site request forgery (CSRF) CVE-2025-14159 | Medium 4.3 | Up to 4.9.2 | Fixed in a later version (latest 5.2.9) | 12 Dec 2025 |
| Sensitive data exposure CVE-2025-14442 | Medium 5.3 | Up to 4.9.2 | Fixed in a later version (latest 5.2.9) | 12 Dec 2025 |
| Broken access control CVE-2025-1404 | Medium 5.3 | Up to 4.4.7 | Fixed in a later version (latest 5.2.9) | 1 Mar 2025 |
| Cross-site scripting (XSS) CVE-2024-6888 | Medium 4.8 | Before 4.1.7 | Fixed in 4.1.7 | 4 Sep 2024 |
| Cross-site scripting (XSS) CVE-2024-6889 | Medium 4.8 | Before 4.1.7 | Fixed in 4.1.7 | 4 Sep 2024 |
| Cross-site scripting (XSS) CVE-2024-6138 | Medium 4.8 | Before 4.0.9 | Fixed in 4.0.9 | 11 Jul 2024 |
| SQL injection CVE-2021-24931 | Critical 9.8 | Before 2.8.2 | Fixed in 2.8.2 | 6 Dec 2021 |
Read the published descriptions
- CVE-2026-9269, 12 Jun 2026
- The Secure Copy Content Protection and Content Locking WordPress plugin before 5.1.5 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 record
- CVE-2026-2367, 25 Feb 2026
- The Secure Copy Content Protection and Content Locking plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'ays_block' shortcode in all versions up to, and including, 5.0.1 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2026-1320, 12 Feb 2026
- The Secure Copy Content Protection and Content Locking plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'X-Forwarded-For' HTTP header in all versions up to, and including, 4.9.8 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2025-14159, 12 Dec 2025
- The Secure Copy Content Protection and Content Locking plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.9.2. This is due to missing nonce validation on the 'ays_sccp_results_export_file' AJAX action. This makes it possible for unauthenticated attackers to export sensitive plugin data including email addresses, IP addresses, physical addresses, user IDs, and other user information via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. The exported data is stored in a publicly accessible file, allowing attackers to receive the sensitive information even though they are not authenticated. CVE record
- CVE-2025-14442, 12 Dec 2025
- The Secure Copy Content Protection and Content Locking plugin for WordPress is vulnerable to sensitive information exposure due to storage of exported CSV files in a publicly accessible directory with predictable filenames in all versions up to, and including, 4.9.2. This makes it possible for unauthenticated attackers to access sensitive user data including emails, IP addresses, usernames, roles, and location data by directly accessing the exported CSV file. CVE record
- CVE-2025-1404, 1 Mar 2025
- The Secure Copy Content Protection and Content Locking plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the ays_sccp_reports_user_search() function in all versions up to, and including, 4.4.7. This makes it possible for unauthenticated attackers to retrieve a list of registered user emails. CVE record
- CVE-2024-6888, 4 Sep 2024
- 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 record
- CVE-2024-6889, 4 Sep 2024
- 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 record
- CVE-2024-6138, 11 Jul 2024
- 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 record
- CVE-2021-24931, 6 Dec 2021
- 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 record
What to do if you run Secure Copy Content Protection and Content Locking
If you run Secure Copy Content Protection and Content Locking, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Secure Copy Content Protection and Content Locking vulnerabilities
Free. We email you when a new vulnerability is published for Secure Copy Content Protection and Content Locking, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.