Multi Scheduler: Cross-site request forgery
Multi Scheduler is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
- Component
- Multi Scheduler
- Plugin slug
multi-scheduler- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Jun 22, 2020
This CVE was published Jun 22, 2020 and is one of 1 known issue for this plugin.
Update, patch or deactivate.
Update Multi Scheduler to a release outside the affected range, or disable and remove it until a fixed version is available.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The Multi-Scheduler plugin 1.0.0 for WordPress has a Cross-Site Request Forgery (CSRF) vulnerability in the forms it presents, allowing the possibility of deleting records (users) when an ID is known.
NVD vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Primary and upstream sources
- NVD record for CVE-2020-13426
- Upstream reference 0day.today
- Upstream reference cxsecurity.com
- Upstream reference infayer.com
- Upstream reference packetstormsecurity.com
- Upstream reference research-labs.net
- Upstream reference twitter.com
- WordPress.org plugin page wordpress.org
- Upstream reference exploit-db.com
- Upstream reference 0day.today
- Upstream reference cxsecurity.com
- Upstream reference infayer.com
- Upstream reference packetstormsecurity.com
- Upstream reference research-labs.net
- Upstream reference twitter.com
- WordPress.org plugin page wordpress.org
- Upstream reference exploit-db.com