CVE-2025-12072

Disable Content Editor For Specific Template <= 2.0 - Cross-Site Request Forgery to Template Configuration Update

MEDIUM
4.3
CVSS Score
Published: October 24, 2025 at 08:23 AM UTC
Updated: October 8, 2026 at 11:10 AM UTC
1 product affected across 1 vendorDisable Content Editor For Specific Template

Using Disable Content Editor For Specific Template by mynamevenu24?

Get instant alerts when new vulnerabilities affect Disable Content Editor For Specific Template - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM4.3
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

4.3MEDIUMWordfence
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-352

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card