The Export All URLs WordPress plugin before 5.1 generates CSV filenames containing posts URLS (including private posts) in a predictable pattern using a random 6-digit number. These files are stored in the publicly accessible wp-content/uploads/ directory. As a result, any unauth...
Product
wordpress export-all-urls vulnerabilities
7 published CVES affecting wordpress export-all-urls, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 7
- Critical
- 0
- High
- 0
- Medium
- 7
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest wordpress export-all-urls CVEs
Newest publication first
-
MediumCVSS 5.3 EPSS 0.31%
-
MediumCVSS 6.1 EPSS 0.56%
The Export All URLs WordPress plugin before 4.6 does not sanitise and escape a parameter before outputting them back in the page, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin
-
CVE-2022-27856 WordPress Export All URLs Plugin <= 4.1 is vulnerable to Cross Site Scripting (XSS)
PublishedMediumCVSS 5.4 EPSS 0.38%Auth. (editor+) Stored Cross-Site Scripting (XSS) vulnerability in Atlas Gondal Export All URLs plugin <= 4.1 versions.
-
MediumCVSS 6.5 EPSS 1.2%
The Export All URLs WordPress plugin before 4.4 does not validate the path of the file to be removed on the system which is supposed to be the CSV file. This could allow high privilege users to delete arbitrary file from the server
-
MediumCVSS 4.8 EPSS 0.53%
Authenticated (editor or higher user role) Stored Cross-Site Scripting (XSS) vulnerability in Export All URLs plugin <= 4.1 at WordPress.
-
MediumCVSS 6.5 EPSS 0.65%
The Export All URLs WordPress plugin before 4.3 does not have CSRF in place when exporting data, which could allow attackers to make a logged in admin export all posts and pages (including private and draft) into an arbitrary CSV file, which the attacker can then download and ret...
-
MediumCVSS 6.1 EPSS 0.80%
The Export All URLs WordPress plugin before 4.2 does not sanitise and escape the CSV filename before outputting it back in the page, leading to a Reflected Cross-Site Scripting
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.