WordPress security by component
WpBookingly
Plugin description
WpBookingly is a WordPress component with 4 published CVE records in this archive. The latest tracked vulnerability was published May 26, 2026; the highest CVE/CNA score is 9.8.
Plugin slug:
service-booking-managerLatest vulnerability
CVE-2026-25444: WpBookingly: A security weakness
WpBookingly 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 published affected range is n/a through 1.2.9.
| Safe version |
|
||
|---|---|---|---|
| May 26, 2026 |
CVE-2026-25444
WpBookingly: A security weakness
WpBookingly 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 published affected range is n/a through 1.2.9.
|
1.3.0 |
CVE4.3
NVDPending
|
| May 20, 2026 |
CVE-2026-27405
WpBookingly: A security weakness
WpBookingly 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 published affected range is n/a through 1.2.9.
|
1.3.0 |
CVE6.5
NVDPending
|
| Mar 13, 2026 |
CVE-2026-32384
WpBookingly: Filesystem traversal
WpBookingly is affected by filesystem traversal. Exposure depends on how the affected operation is made reachable by the site. A crafted path can escape the intended directory and reach files or directories elsewhere on the server.
|
See mitigation notes |
CVE7.5
NVDPending
|
| Apr 11, 2025 |
CVE-2025-32607
WpBookingly: Code execution
WpBookingly is affected by code execution. Exposure depends on how the affected operation is made reachable by the site. Successful exploitation can run attacker-controlled code in the WordPress hosting account.
|
See mitigation notes |
CVE9.8
NVDPending
|