CVE-2025-1757: The WordPress Portfolio Builder – Portfolio Gallery plugin for WordPress is vulnerable to Stored Cross-Site Sc

Q: How do I fix CVE-2025-1757?

portfoliohub: upgrade to newer than 1.1.7. Exact commands for each OS are on this page.

Q: Is CVE-2025-1757 being exploited?

CVE-2025-1757 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-1757 affect?

CVE-2025-1757 affects portfoliohub. Severity is medium (CVSS 6.4). The WordPress Portfolio Builder – Portfolio Gallery plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'pfhub_portfolio' and 'pfhub_portfolio_portfolio' shortcodes in all versions up to, and including, 1.1.7

Q: How urgent is CVE-2025-1757?

Priority 27/100. No elevated risk signals yet.

Routine

MEDIUM 6.4UPGRADE

CVE-2025-1757 is a medium-severity flaw (CVSS 6.4) affecting portfoliohub. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The WordPress Portfolio Builder – Portfolio Gallery plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'pfhub_portfolio' and 'pfhub_portfolio_portfolio' shortcodes in all versions up to, and including, 1.1.7 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scrip

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	6.4 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 80%)
CISA exploited list	No
Weakness	CWE-79
Published	2025-02-28
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: portfoliohub

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-02-28 05:15 UTCPublished CVE record published
2026-06-17 08:39 UTCUpdated Record last modified

portfoliohub portfoliohub UPGRADE

Affected: <= 1.1.7

Fixed in: newer than 1.1.7

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy portfoliohub || rpm -q portfoliohub || portfoliohub --version

2. UPGRADE to newer than 1.1.7 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade portfoliohub

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade portfoliohub

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-1757?

portfoliohub: upgrade to newer than 1.1.7. Exact commands for each OS are on this page.

Is CVE-2025-1757 being exploited?

CVE-2025-1757 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-1757 affect?

CVE-2025-1757 affects portfoliohub. Severity is medium (CVSS 6.4). The WordPress Portfolio Builder – Portfolio Gallery plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'pfhub_portfolio' and 'pfhub_portfolio_portfolio' shortcodes in all versions up to, and including, 1.1.7

How urgent is CVE-2025-1757?

Priority 27/100. No elevated risk signals yet.

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs