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.
Metrics
Affected Vendors & Products
References
History
Mon, 27 Oct 2025 22:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Wordpress
Wordpress wordpress |
|
| Vendors & Products |
Wordpress
Wordpress wordpress |
Fri, 24 Oct 2025 17:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 24 Oct 2025 08:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Disable Content Editor For Specific Template <= 2.0 - Cross-Site Request Forgery to Template Configuration Update | |
| Weaknesses | CWE-352 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: Wordfence
Published: 2025-10-24T08:23:56.994Z
Updated: 2025-10-24T16:45:11.243Z
Reserved: 2025-10-22T14:07:11.906Z
Link: CVE-2025-12072
Updated: 2025-10-24T16:39:58.394Z
Status : Awaiting Analysis
Published: 2025-10-24T09:15:44.733
Modified: 2025-10-27T13:20:15.637
Link: CVE-2025-12072
No data.