CVE-2018-5673: CSRF
First published: Sat Jan 13 2018(Updated: )
An issue was discovered in the booking-calendar plugin 2.1.7 for WordPress. CSRF exists via wp-admin/admin.php.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Booking Calendar | =2.1.7 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2018-5673?
CVE-2018-5673 has been classified as a medium severity vulnerability due to the potential for CSRF attacks.
How do I fix CVE-2018-5673?
To fix CVE-2018-5673, update the booking-calendar plugin to version 2.1.8 or later.
What types of attacks can CVE-2018-5673 facilitate?
CVE-2018-5673 can facilitate Cross-Site Request Forgery (CSRF) attacks, allowing an attacker to perform unauthorized actions as an authenticated user.
Which version of the booking calendar plugin is affected by CVE-2018-5673?
Version 2.1.7 of the booking-calendar plugin for WordPress is affected by CVE-2018-5673.
Is there a known exploit for CVE-2018-5673?
Yes, there are known exploits for CVE-2018-5673 that can take advantage of the CSRF vulnerability.
- agent/references
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/author
- agent/last-modified-date
- agent/event
- agent/first-publish-date
- agent/description
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- agent/weakness
- agent/softwarecombine
- vendor/booking calendar project
- canonical/booking calendar
- version/booking calendar/2.1.7