dbcve.org
PortfoliohubWordPress extension

CVE-2025-1757

MEDIUM · 5.4 CVSS v3.1 Published 2025-02-28
Fix available
A fix is available. Upgrade to after 1.1.7 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 scripts in pages that will execute whenever a user accesses an injected page.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The WordPress Portfolio Builder – Portfolio Gallery plugin fails to properly sanitize and escape user-supplied attributes in the 'pfhub_portfolio' and 'pfhub_portfolio_portfolio' shortcodes. This allows authenticated contributors+ to inject malicious JavaScript that executes in browsers of users viewing affected pages, representing a stored XSS vulnerability.

MitigationUpdate the plugin to version 1.1.8 or later which includes proper input sanitization using WordPress sanitization functions (like sanitize_text_field) and output escaping (like esc_attr) for all shortcode attributes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PortfoliohubWordPress extension
Affected:<= 1.1.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify plugin installation and version
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate 'Portfolio Builder - Portfolio Gallery' or 'Portfoliohub Portfolio' plugin, and record the installed version number.
    Affected if Plugin version is 1.1.7 or lower (the vulnerable range)
  2. Detect vulnerable shortcode usage in content
    Search WordPress database for instances of '[pfhub_portfolio' or '[pfhub_portfolio_portfolio' shortcodes in posts, pages, or custom post types. Use WP-CLI: wp db query "SELECT * FROM wp_posts WHERE post_content LIKE '%[pfhub_portfolio%'" or inspect content via admin editor.
    Affected if One or more posts/pages contain either shortcode and the plugin version is <= 1.1.7
  3. Verify shortcode attributes are present
    Examine a post containing the shortcode in the editor (Visual or Text mode). Look for any custom attributes added to the shortcode tag, such as category, id, or style parameters.
    Affected if Shortcode has custom attributes and the plugin version is <= 1.1.7 (attributes are what get exploited)
  4. Check for contributor-level or higher user accounts
    Navigate to Users > All Users in WordPress admin. Review user roles to identify any accounts with Contributor, Author, Editor, or Administrator roles.
    Affected if Any authenticated user with Contributor+ access exists and the vulnerable shortcode is in use

User is affected if the plugin version is 1.1.7 or lower AND the pfhub_portfolio or pfhub_portfolio_portfolio shortcode is present in any published content with custom attributes.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 1.1.7
Interim mitigation

Update the plugin to version 1.1.8 or later which includes proper input sanitization using WordPress sanitization functions (like sanitize_text_field) and output escaping (like esc_attr) for all shortcode attributes.

Fix this in Portfoliohub Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1757 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-1757 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data