Unknown Eazydocs vulnerabilities

4 known vulnerabilities affecting unknown/eazydocs.

Total CVEs
4
CISA KEV
0
Public exploits
0
Exploited in wild
0
Severity breakdown
HIGH3MEDIUM1

Vulnerabilities

Page 1 of 1
CVE-2024-3999MEDIUMCVSS 4.8fixed in 2.5.02024-07-02
CVE-2024-3999 [MEDIUM] CWE-79 CVE-2024-3999: The EazyDocs WordPress plugin before 2.5.0 does not sanitise and escape some of its settings, which The EazyDocs WordPress plugin before 2.5.0 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup)
cvelistv5nvd
CVE-2024-0248HIGHCVSS 7.5≥ 2.3.8, < 2.4.02024-02-12
CVE-2024-0248 [HIGH] CWE-862 EazyDocs < 2.4.0 - Subscriber+ Arbitrary Posts Deletion and Document Management EazyDocs < 2.4.0 - Subscriber+ Arbitrary Posts Deletion and Document Management The EazyDocs WordPress plugin before 2.4.0 re-introduced CVE-2023-6029 (https://wpscan.com/vulnerability/7a0aaf85-8130-4fd7-8f09-f8edc929597e/) in 2.3.8, allowing any authenticated users, such as subscriber to delete arbitrary posts, as well as add and delete documents/sections. The issue was partially fixed
cvelistv5
CVE-2023-6029HIGHCVSS 7.5≥ 2.3.8, < 2.4.02024-01-15
CVE-2023-6029 [HIGH] CWE-862 CVE-2023-6029: The EazyDocs WordPress plugin before 2.3.6 does not have authorization and CSRF checks when handling The EazyDocs WordPress plugin before 2.3.6 does not have authorization and CSRF checks when handling documents and does not ensure that they are documents from the plugin, allowing unauthenticated users to delete arbitrary posts, as well as add and delete documents/sections.
cvelistv5nvd
CVE-2023-6035HIGHCVSS 8.8fixed in 2.3.42023-12-11
CVE-2023-6035 [HIGH] CWE-89 CVE-2023-6035: The EazyDocs WordPress plugin before 2.3.4 does not properly sanitize and escape "data" parameter be The EazyDocs WordPress plugin before 2.3.4 does not properly sanitize and escape "data" parameter before using it in an SQL statement via an AJAX action, which could allow any authenticated users, such as subscribers, to perform SQL Injection attacks.
cvelistv5nvd