CVE-2025-12072 Disable Content Editor For Specific Template <= 2.0 - Cross-Site Request Forgery to Template Configuration Update
Unauthenticated attackers can modify template configurations by tricking administrators into clicking a link due to missing nonce validation.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2025-12072?
CVE-2025-12072 is a medium-severity vulnerability in mynamevenu24 Disable Content Editor For Specific Template, published on 24 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official 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.
Weakness: CWE-352
Which versions are affected by CVE-2025-12072?
How do I fix CVE-2025-12072?
No fix has been published for CVE-2025-12072 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-12072 being exploited?
There is no known exploitation of CVE-2025-12072 in the wild and no public exploit code.
Sources
Also known as GHSA-g32w-vwf2-848m.