← WordPress Vulnerabilities
WordPress security by component

WPZOOM Portfolio

WPZOOM Portfolio is a WordPress component with 4 published CVE records in this archive. The latest tracked vulnerability was published Jul 13, 2026; the highest CVE/CNA score is 7.1.

Plugin slug: wpzoom-portfolio

CVE-2026-57712: WPZOOM Portfolio: Cross-site scripting

WPZOOM Portfolio 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. The published affected range is <= 1.4.29.

PublishedJul 13, 2026
Known safe version1.4.30
Safe version
Jul 13, 2026 CVE-2026-57712
WPZOOM Portfolio: Cross-site scripting
WPZOOM Portfolio 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. The published affected range is <= 1.4.29.
1.4.30
CVE7.1
NVDPending
Jun 10, 2026 CVE-2026-49069
WPZOOM Portfolio: Cross-site scripting
WPZOOM Portfolio 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. The published affected range is n/a through 1.4.21.
1.4.22
CVE7.1
NVDPending
Aug 31, 2024 CVE-2024-8276
WPZOOM Portfolio Lite – Filterable Portfolio Plugin: Cross-site scripting
WPZOOM Portfolio Lite – Filterable Portfolio Plugin is affected by cross-site scripting. Exploitation requires at least contributor-level access. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE6.4
NVD5.4
Jan 23, 2023 CVE-2022-4789
WPZOOM Portfolio: Cross-site scripting
WPZOOM Portfolio 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
CVE5.4
NVD5.4