WordPress plugin
Disable Content Editor For Specific Template security & vulnerabilities
Unpatched vulnerability in the latest version
At least one vulnerability affects the latest version and no fix has been released. Deactivate the plugin or restrict access to the affected feature until the vendor ships a patch.
- Critical0
- High0
- Medium1
- Low0
All Disable Content Editor For Specific Template vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium4.3 | Cross-Site Request Forgery to Template Configuration Update ≤2.0No patch available | CVE-2025-12072 |
- Medium4.3Cross-Site Request Forgery to Template Configuration Update
≤2.0No patch available
Disable Content Editor For Specific Template: common questions
Does Disable Content Editor For Specific Template have known vulnerabilities?
Yes. VulnCrest Radar lists 1 known vulnerability in Disable Content Editor For Specific Template: 1 medium. At least one is not fixed in the latest version.
How do I check which version of Disable Content Editor For Specific Template I run?
In wp-admin open Plugins → Installed Plugins; the version is shown under the name. Without admin access, our passive Check my site tool can often read it from public files.
What is the most recent Disable Content Editor For Specific Template vulnerability?
CVE-2025-12072, published Oct 23, 2025: Disable Content Editor For Specific Template <= 2.0 - Cross-Site Request Forgery to Template Configuration Update. Severity: Medium (CVSS 4.3).
Is any Disable Content Editor For Specific Template vulnerability listed in CISA KEV?
No. None of the known Disable Content Editor For Specific Template vulnerabilities is currently listed in the CISA KEV catalog.