WordPress security by component
Content Control
Plugin description
Content Control is a WordPress component with 4 published CVE records in this archive. The latest tracked vulnerability was published Jul 23, 2026; the highest CVE/CNA score is 6.5.
Plugin slug:
content-controlLatest vulnerability
CVE-2026-65485: Content Control: A security weakness
Content Control 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. The published affected range is n/a through 2.6.5.
| Safe version |
|
||
|---|---|---|---|
| Jul 23, 2026 |
CVE-2026-65485
Content Control: A security weakness
Content Control 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. The published affected range is n/a through 2.6.5.
|
> 2.6.5 |
CVE5.3
NVDPending
|
| May 07, 2025 |
CVE-2025-47501
Content Control: Cross-site scripting
Content Control 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 |
CVE6.5
NVDPending
|
| Mar 05, 2025 |
CVE-2024-11153
Ultimate Content Restriction Plugin! Restrict Content, Create Conditional Blocks & More: Sensitive information exposure
Ultimate Content Restriction Plugin! Restrict Content, Create Conditional Blocks & More 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
|
| Jan 23, 2023 |
CVE-2022-4509
Content Control: Cross-site scripting
Content Control 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.4
NVD5.4
|