PortfoliohubWordPress extension
CVE-2024-13231
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 · uneditedThe WordPress Portfolio Builder – Portfolio Gallery plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'add_video' function in all versions up to, and including, 1.1.7. This makes it possible for unauthenticated attackers to add arbitrary videos to any portfolio gallery.
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 confidenceThe WordPress Portfolio Builder – Portfolio Gallery plugin lacks a capability check on the 'add_video' function, allowing unauthenticated attackers to add arbitrary videos to any portfolio gallery. This is a broken access control vulnerability (CWE-862) where the function relies on no authorization mechanism.
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
<= 1.1.7CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify plugin is installedCheck your WordPress plugins directory or WordPress admin panel for 'Portfolio Builder - Portfolio Gallery' or 'Portfoliohub Portfoliohub' in the list of active pluginsAffected if The plugin appears in your WordPress installation
-
Identify installed versionLook in the plugin's main PHP file (usually in wp-content/plugins/portfolio-builder-portfolio-gallery/) for the 'Version' header in the plugin comment block, or check the WordPress plugin admin pageAffected if Version is 1.1.7 or lower
-
Confirm vulnerable function existsInspect the plugin files for the 'add_video' function - typically found in the main plugin PHP file or an AJAX handler file. Search for 'function add_video' or 'add_video' action hooksAffected if The add_video function exists in the code without a capability check (like 'current_user_can' or 'wp_verify_nonce')
-
Check unauthenticated access exposureTest if the add_video AJAX action or direct function call is accessible without authentication - examine if the function is hooked to wp_ajax_nopriv_ or has no auth verificationAffected if The function can be called without authentication (no current_user_can check before execution)
You are affected if the Portfolio Builder - Portfolio Gallery plugin is installed at version 1.1.7 or lower and the add_video function is accessible without authentication or capability verification.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the plugin to version 1.1.8 or later, which should include proper capability checks. Until then, consider disabling the plugin or restricting access at the server level.
Fix this in Portfoliohub
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13231 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-13231 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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