Disable Content Editor For Specific Template <= 2.0 - Cross-Site Request Forgery to Template Configuration Update
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| mynamevenu24 | Disable Content Editor For Specific Template | unaffected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Wordpress | Wordpress | — |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.133% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Wordpress
Wordpress wordpress |
|
| Vendors & Products |
Wordpress
Wordpress wordpress |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| 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
|