fixnx
highCVE-2026-57712

WPZOOM Portfolio Lite – Filterable Portfolio Plugin <= 1.4.29 - Unauthenticated Stored Cross-Site Scripting

WPZOOM Portfolio Lite – Filterable Portfolio Plugin has a cross-site scripting issue. Unsafe script can run in another user's browser if the vulnerable feature is used.

ProductWPZOOM Portfolio Lite – Filterable Portfolio Plugin
CVSS7.1
EPSS0.0018
UpdatedJuly 15, 2026

Quick answer

WPZOOM Portfolio Lite – Filterable Portfolio Plugin should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.

Who is affected

Affected versions

  • WPZOOM Portfolio Lite – Filterable Portfolio Plugin up to and including 1.4.29

Fixed versions

  • WPZOOM Portfolio Lite – Filterable Portfolio Plugin 1.4.30 or later

How to fix it

Update WPZOOM Portfolio Lite – Filterable Portfolio Plugin. The old version can let unsafe script run in a user or admin browser.

  1. Back up the site and database.
  2. Update WPZOOM Portfolio Lite – Filterable Portfolio Plugin to WPZOOM Portfolio Lite – Filterable Portfolio Plugin 1.4.30 or later.
  3. Clear all site and plugin caches.
  4. Review recent posts, settings, forms, and widgets for unknown script.

Scan now. Google sign-in is only needed to unlock fix guidance.

Verify the fix

  • Confirm the installed version is WPZOOM Portfolio Lite – Filterable Portfolio Plugin 1.4.30 or later.
  • Test the affected feature and confirm script input is blocked or cleaned.

Related categories

WordPressBrowserCross-site Scripting

Trusted references

Wordfence advisoryWordfence, NVDSource advisoryWordfence, NVDSource advisoryWordfence, NVD

FAQ

What is affected by CVE-2026-57712?

WPZOOM Portfolio Lite – Filterable Portfolio Plugin versions listed as affected should be reviewed: WPZOOM Portfolio Lite – Filterable Portfolio Plugin up to and including 1.4.29.

What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.