Disable Content Editor For Specific Template
Approved changes feed: RSS · Atom
cpe:2.3:a:mynamevenu24:disable_content_editor_for_specific_template:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Mynamevenu24 (892bc2e6-acb1-5ac5-aa14-21bfcf2089b3) |
|---|---|
| Product | Disable Content Editor For Specific Template (94ef800b-7759-50a7-9b66-01e1610e6fee) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-12072 |
vulnerable | 2026-06-08 07:04:29.642438 |
Disable Content Editor For Specific Template <= 2.0 - Cross-Site Request Forgery to Template Configuration Update
MEDIUM (4.3)
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.
Published: 2025-10-24T08:23:56.994Z
Updated: 2026-04-08T16:42:10.290Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.