WordPress security by component
Calendarista Basic Edition
Plugin description
Calendarista Basic Edition is a WordPress component with 3 published CVE records in this archive. The latest tracked vulnerability was published Jun 09, 2024; the highest published CVSS base score is 7.1.
Plugin slug:
calendarista-basic-editionLatest vulnerability
CVE-2024-30534: Calendarista Basic Edition: A security weakness
Calendarista Basic Edition is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
| Safe version |
|
||
|---|---|---|---|
| Jun 09, 2024 |
CVE-2024-30534
Calendarista Basic Edition: A security weakness
Calendarista Basic Edition is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVE6.5
NVD9.8
|
| Apr 15, 2024 |
CVE-2024-31942
Calendarista Basic Edition: Cross-site request forgery
Calendarista Basic Edition 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. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVE4.3
NVDPending
|
| Mar 21, 2024 |
CVE-2024-27993
Calendarista Basic Edition: Cross-site scripting
Calendarista Basic Edition is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVE7.1
NVDPending
|