WordPress security by component
Secure Copy Content Protection and Content Locking
Plugin description
Secure Copy Content Protection and Content Locking is a WordPress component with 9 published CVE records in this archive. The latest tracked vulnerability was published Feb 25, 2026; the highest CVE/CNA score is 7.1.
Plugin slug:
secure-copy-content-protectionLatest vulnerability
CVE-2026-2367: Secure Copy Content Protection and Content Locking: Cross-site scripting
Secure Copy Content Protection and Content Locking is affected by cross-site scripting. Exploitation requires at least contributor-level access. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
| Safe version |
|
||
|---|---|---|---|
| Feb 25, 2026 |
CVE-2026-2367
Secure Copy Content Protection and Content Locking: Cross-site scripting
Secure Copy Content Protection and Content Locking is affected by cross-site scripting. Exploitation requires at least contributor-level access. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE6.4
NVDPending
|
| Feb 19, 2026 |
CVE-2026-25335
Secure Copy Content Protection and Content Locking: A security weakness
Secure Copy Content Protection and Content Locking is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE4.3
NVDPending
|
| Dec 12, 2025 |
CVE-2025-14442
Secure Copy Content Protection and Content Locking: Sensitive information exposure
Secure Copy Content Protection and Content Locking is affected by sensitive information exposure. The vulnerable path is reachable without authentication. Successful exploitation can disclose data that should not be available to the caller.
|
See mitigation notes |
CVE5.3
NVDPending
|
| Dec 12, 2025 |
CVE-2025-14159
Secure Copy Content Protection and Content Locking: Cross-site request forgery
Secure Copy Content Protection and Content Locking is affected by cross-site request forgery. The vulnerable path is reachable without authentication. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
|
See mitigation notes |
CVE4.3
NVDPending
|
| Apr 04, 2025 |
CVE-2025-32133
Secure Copy Content Protection and Content Locking: Cross-site scripting
Secure Copy Content Protection and Content Locking is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE5.9
NVDPending
|
| Apr 01, 2025 |
CVE-2025-30905
Secure Copy Content Protection and Content Locking: Cross-site scripting
Secure Copy Content Protection and Content Locking is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE7.1
NVDPending
|
| Mar 01, 2025 |
CVE-2025-1404
Secure Copy Content Protection and Content Locking: A security weakness
Secure Copy Content Protection and Content Locking is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE5.3
NVDPending
|
| Jun 09, 2024 |
CVE-2024-32787
Secure Copy Content Protection and Content Locking: A security weakness
Secure Copy Content Protection and Content Locking is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE4.3
NVDPending
|
| Apr 29, 2024 |
CVE-2024-33587
Secure Copy Content Protection and Content Locking: A security weakness
Secure Copy Content Protection and Content Locking is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE5.3
NVDPending
|