dbcve.org
Wp PortfolioWordPress extension · Themehorse

CVE-2024-33537

MEDIUM · 6.5 CVSS v3.1 Published 2024-04-29
Fix available
A fix is available. Upgrade to 2.5 or later.
See remediation →
69/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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Theme Horse WP Portfolio allows Stored XSS.This issue affects WP Portfolio: from n/a through 2.4.

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 · moderate confidence

Stored Cross-site Scripting (XSS) vulnerability in the Theme Horse WP Portfolio WordPress plugin allows authenticated attackers to inject malicious JavaScript code through unsanitized input fields. This injected script executes in the browsers of other users viewing the affected portfolio content, potentially leading to session hijacking or credential theft.

MitigationUpdate WP Portfolio to the latest version when available. In the interim, implement proper input validation and output encoding on all user-supplied data, and consider restricting administrative access to trusted personnel only.

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
Wp PortfolioWordPress extension
Affected:< 2.5

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
Low

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

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. Check if WP Portfolio plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'WP Portfolio' or 'WP Portfolio by Theme Horse' in the plugin list.
    Affected if Plugin is not installed or not present in the plugin list
  2. Identify installed WP Portfolio version
    In the Plugins list, locate WP Portfolio and note the version number displayed beneath the plugin name. Alternatively, check the plugin files: /wp-content/plugins/wp-portfolio/readme.txt or /wp-content/plugins/wp-portfolio/wp-portfolio.php for the 'Version' header.
    Affected if Version number is less than 2.5 or cannot be determined (plugin may be outdated)
  3. Verify portfolio post types exist
    In WordPress admin, look for a 'Portfolio' post type in the left sidebar menu. Click to view existing portfolio entries.
    Affected if No portfolio content exists - the vulnerability only affects portfolio entries that are created and displayed
  4. Inspect portfolio input fields for unencoded content
    Edit an existing portfolio entry or create a new one. Check fields such as title, description, client name, and custom fields. View the page source of the portfolio archive or single template to see if field values are output without HTML encoding (look for raw user input appearing as raw HTML rather than escaped).
    Affected if User-supplied portfolio data appears as raw HTML in the source or displays unescaped characters when viewed

User is affected if WP Portfolio plugin is installed with version less than 2.5 AND portfolio content with user-supplied fields is being displayed on the site.

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.

dbcve · scoped
Upgrade available Upgrade to 2.5 or later
Fixed in 2.5
Interim mitigation

Update WP Portfolio to the latest version when available. In the interim, implement proper input validation and output encoding on all user-supplied data, and consider restricting administrative access to trusted personnel only.

Recommended fix Moderate confidence

WP Portfolio version 2.5

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the WP Portfolio plugin
  4. Check if the current version is below 2.5
  5. If vulnerable, click 'Update Now' to upgrade to version 2.5 or later
  6. Verify the update completed successfully

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wp Portfolio Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-33537 — 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-2024-33537 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