WordPress security by component
Directory Pro
Plugin description
Directory Pro is a WordPress component with 5 published CVE records in this archive. The latest tracked vulnerability was published Mar 05, 2026; the highest CVE/CNA score is 8.8.
Plugin slug:
directory-proLatest vulnerability
CVE-2026-27396: Directory Pro: A security weakness
Directory Pro 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.
| Safe version |
|
||
|---|---|---|---|
| Mar 05, 2026 |
CVE-2026-27396
Directory Pro: A security weakness
Directory Pro 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.
|
See mitigation notes |
CVE7.3
NVDPending
|
| Dec 16, 2025 |
CVE-2025-64243
Directory Pro: A security weakness
Directory Pro 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.
|
See mitigation notes |
CVE4.3
NVDPending
|
| Oct 22, 2025 |
CVE-2025-52748
Directory Pro: Cross-site scripting
Directory Pro is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE7.1
NVDPending
|
| Sep 22, 2025 |
CVE-2025-57948
Directory Pro: Cross-site scripting
Directory Pro is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE6.5
NVDPending
|
| Mar 27, 2023 |
CVE-2020-36666
directory-pro: A security weakness
directory-pro 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.
|
See mitigation notes |
CVE8.8
NVD8.8
|