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–4 of 4 vulnerabilities matching your filters

Known WordPress vulnerabilities, page 1 of 1
Severity Component Vulnerability Affected versions Published CVE Source
– Not scored User Private Files Plugin user-private-files Information Disclosure Unauthenticated Private File Disclosure via .htaccess Rewrite Rule Bypass (Multisite) < 2.2.0 Fixed in 2.2.0 CVE-2026-97332 WPScan
6.4 Medium File Sharing & Download Manager Plugin user-private-files Cross-Site Scripting Authenticated (Subscriber+) Stored Cross-Site Scripting via 'fldr_ttl' Parameter ≤ 2.1.6 CVE-2026-10093 Wordfence
6.4 Medium User Private Files – File Upload & Download Manager with Secure File Sharing Plugin user-private-files Arbitrary File Upload File Upload & Download Manager with Secure File Sharing <= 2.1.3 - Authenticated (Subscriber+) Stored Cross-Site Scripting ≤ 2.1.3 CVE-2024-13799 Wordfence
4.3 Medium User Private Files Plugin user-private-files Broken Access Control Insecure Direct Object Reference to Authenticated (Subscriber+) Private File Access ≤ 2.1.0 CVE-2024-7848 Wordfence

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