CVE-2025-12072
Disable Content Editor For Specific Template <= 2.0 - Cross-Site Request Forgery to Template Configuration Update
CVSS Score
4.3
EPSS Score
0.0%
EPSS Percentile
0th
The Disable Content Editor For Specific Template plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.0. This is due to missing nonce validation on template configuration updates. This makes it possible for unauthenticated attackers to add or delete template configurations via a forged request granted they can trick an administrator into performing an action such as clicking on a link.
| CWE | CWE-352 |
| Vendor | mynamevenu24 |
| Product | disable content editor for specific template |
| Published | Oct 24, 2025 |
| Last Updated | Apr 8, 2026 |
Stay Ahead of the Next One
Get instant alerts for mynamevenu24 disable content editor for specific template
Be the first to know when new medium vulnerabilities affecting mynamevenu24 disable content editor for specific template are published — delivered to Slack, Telegram or Discord.
Get Free Alerts →
Free · No credit card · 60 sec setup
CVSS v3 Breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N Attack Vector
Attack Complexity
Privileges Required
User Interaction
Scope
Confidentiality
Integrity
Availability
Affected Versions
mynamevenu24 / Disable Content Editor For Specific Template
0 ≤ 2.0
References
Credits
Nabil Irawan