WordPress plugin · secure-copy-content-protection
Is Secure Copy Content Protection and Content Locking safe?
Safe on 5.3.2 or newer.
The current version, 5.3.2, is past every affected range on record (15 of 15 records list one). Keep it updated and you’re clear of them.
- Flaws on record
- 15
- High or critical
- 3
- Exploited
- none
- Current version
- 5.3.2
- Last updated
- Oct 23, 2026
- Active installs
- 20,000+
Every recorded flaw
- Jun 12, 2026Secure Copy Content Protection and Content Locking: Does not sanitise and escape some of its settingsCVE-2026-9269 · fixed in 5.1.5 · reported by WPScanLow 3.5
- Feb 25, 2026Secure Copy Content Protection and Content Locking: Stored Cross-Site ScriptingCVE-2026-2367 · affects up to 5.0.1 · reported by WordfenceMedium 6.4
- Feb 19, 2026Secure Copy Content Protection and Content Locking: Missing AuthorizationCVE-2026-25335 · affects up to 5.0.0 · reported by PatchstackMedium 4.3
- Feb 12, 2026Secure Copy Content Protection and Content Locking: Stored Cross-Site ScriptingCVE-2026-1320 · affects up to 4.9.8 · reported by WordfenceHigh 7.2
- Dec 12, 2025Secure Copy Content Protection and Content Locking: Sensitive information exposureCVE-2025-14442 · affects up to 4.9.2 · reported by WordfenceMedium 5.3
- Dec 12, 2025Secure Copy Content Protection and Content Locking: Cross-Site Request ForgeryCVE-2025-14159 · affects up to 4.9.2 · reported by WordfenceMedium 4.3
- Apr 4, 2025Secure Copy Content Protection and Content Locking: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')CVE-2025-32133 · affects up to 4.5.5 · reported by PatchstackMedium 5.9
- Apr 1, 2025Secure Copy Content Protection and Content Locking: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')CVE-2025-30905 · affects up to 4.4.3 · reported by PatchstackHigh 7.1
- Mar 1, 2025Secure Copy Content Protection and Content Locking: Unauthorized access of dataCVE-2025-1404 · affects up to 4.4.7 · reported by WordfenceMedium 5.3
- Sep 4, 2024Secure Copy Content Protection and Content Locking: Does not sanitise and escape some of its settingsCVE-2024-6889 · fixed in 4.1.7 · reported by WPScanMedium 4.8
- Sep 4, 2024Secure Copy Content Protection and Content Locking: Does not sanitise and escape some of its settingsCVE-2024-6888 · fixed in 4.1.7 · reported by WPScanMedium 4.8
- Jul 11, 2024Secure Copy Content Protection and Content Locking: Does not sanitise and escape some of its settingsCVE-2024-6138 · fixed in 4.0.9 · reported by WPScanMedium 4.8
- Jun 9, 2024Secure Copy Content Protection and Content Locking: Missing AuthorizationCVE-2024-32787 · affects up to 3.7.1 · reported by PatchstackMedium 4.3
- Apr 29, 2024Secure Copy Content Protection and Content Locking: Missing AuthorizationCVE-2024-33587 · affects up to 3.9.0 · reported by PatchstackMedium 5.3
- Dec 6, 2021Secure Copy Content Protection and Content Locking: 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 SCVE-2021-24931 · fixed in 2.8.2 · reported by WPScan79% oddsCritical 9.8
Records come from the National Vulnerability Database, published by the researchers who found each flaw (Wordfence, Patchstack, WPScan and others); exploited status from CISA; exploit odds from FIRST’s EPSS; current version, installs and closures from wordpress.org, checked daily. Want every plugin on your site checked at once? Run the free website check.
Weekly security brief
The flaws that hit local websites, every Friday.
One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.
Tell us what you're building.
A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.
Not ready to talk yet? Run the free website check and see what Google sees.