WordPress vulnerability database

Every CVE published for WordPress core, plugins and themes since January 2024: 29,007 vulnerabilities, 1,391 of them in the last 30 days. The list is updated every day from the CVE List.

Severity is the CVSS 3.1 base score. Select a band to list only those. Last updated October 5, 2026.

Showing 1–10 of 10 vulnerabilities matching your filters

Known WordPress vulnerabilities, page 1 of 1
Severity Component Vulnerability Affected versions Published CVE Source
5.4 Medium WpTravelly Plugin tour-booking-manager Broken Access Control ≤ 2.3.1 Fixed in 2.3.2 CVE-2026-62063 Patchstack
7.5 High WpTravelly Plugin tour-booking-manager Authentication Bypass Bypass Vulnerability No login needed ≤ 2.1.7 Fixed in 2.1.8 CVE-2026-27089 Patchstack
6.3 Medium WpTravelly Plugin tour-booking-manager Broken Access Control ≤ 2.1.5 Fixed in 2.1.6 CVE-2026-27331 Patchstack
4.3 Medium WpTravelly Plugin tour-booking-manager Broken Access Control ≤ 2.1.7 Fixed in 2.1.8 CVE-2026-39565 Patchstack
8.8 High WpTravelly Plugin tour-booking-manager PHP Object Injection ≤ 1.8.7 Fixed in 1.8.8 CVE-2025-30892 Patchstack
8.8 High WpTravelly Plugin tour-booking-manager Local File Inclusion ≤ 1.8.7 Fixed in 1.8.8 CVE-2025-30891 Patchstack
5.3 Medium WpTravelly Plugin tour-booking-manager Broken Access Control No login needed ≤ 1.8.5 Fixed in 1.8.6 CVE-2025-22737 Patchstack
7.5 High WpTravelly Plugin tour-booking-manager Broken Access Control No login needed ≤ 1.7.7 Fixed in 1.7.8 CVE-2024-43212 Patchstack
5.3 Medium WordPress Tour & Travel Booking Plugin for WooCommerce – WpTravelly Plugin tour-booking-manager Broken Access Control WpTravelly <= 1.7.1 - Missing Authorization via ttbm_new_place_save No login needed ≤ 1.7.1 CVE-2024-0434 Wordfence
4.3 Medium WpTravelly Plugin tour-booking-manager Cross-Site Request Forgery No login needed ≤ 1.6.0 Fixed in 1.6.1 CVE-2024-32450 Patchstack

About this data

Where it comes from
Each row is a record from the CVE List, published by the organization that handled the report: most often Wordfence, Patchstack or WPScan. The CVE ID links to that publisher's advisory.
What is included
CVEs published since January 1, 2024 for WordPress core, plugins and themes, premium ones included. Vulnerabilities that never received a CVE ID are not listed, and rejected CVEs are removed.
Severity
The CVSS 3.1 base score set by the publisher, or by CISA when the publisher gave none. "No login needed" means the score assumes an attacker without an account.
Affected versions
The range the publisher marked as vulnerable. When the record also names the first fixed release, it is shown under the range. If your version is newer than every affected one, that CVE does not apply to you.
Updates
Every day, after the CVE List publishes its end-of-day changes.

This website uses cookies to enhance your browsing experience and ensure the site functions properly. By continuing to use this site, you acknowledge and accept our use of cookies.

Accept All Accept Required Only