Disable Content Editor For Specific Template <= 2.0 - Cross-Site Request Forgery to Template Configuration Update
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 4.3epss 0.1%
exploitation probability
0.1%top 97% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Affected products
mynamevenu24 · Disable Content Editor For Specific Template