dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2024-3808

HIGH · 8.8 CVSS v3.1 Published 2024-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 Porto Theme - Functionality plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 3.1.0 via the 'porto_portfolios' shortcode 'portfolio_layout' attribute. This makes it possible for authenticated attackers, with contributor-level and above permissions, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where php file type can be uploaded and included.

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 Porto Theme WordPress plugin up to version 3.1.0 contains a Local File Inclusion vulnerability in the 'porto_portfolios' shortcode's 'portfolio_layout' attribute. Authenticated users with contributor-level or higher permissions can supply malicious file paths to include and execute arbitrary PHP files on the server, enabling code execution and bypass of access controls.

MitigationUpdate the Porto Theme - Functionality plugin to version 3.1.1 or later, which contains the patch. Until then, restrict contributor-level user permissions and consider disabling the affected shortcode if possible.

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

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 Porto Theme plugin installation and version
    In WordPress admin, go to Appearance > Themes to confirm Porto theme is active. For the plugin version, check Plugins > Installed Plugins and look for 'Porto Theme - Functionality' or 'Porto Theme' plugin. The version number is displayed there.
    Affected if The version listed is 3.1.0 or lower (any version up to and including 3.1.0)
  2. Confirm the shortcode is registered
    Search the plugin files for 'porto_portfolios' shortcode registration, typically in the plugin's main PHP file or includes/shortcodes directory. The shortcode should be registered with add_shortcode('porto_portfolios', ...).
    Affected if The shortcode 'porto_portfolios' is present in the plugin code and registered for use
  3. Check for contributor-level or higher user accounts
    In WordPress admin, go to Users > All Users. Review the role column for any accounts with Contributor, Author, Editor, or Administrator roles. These roles have permissions at or above contributor level.
    Affected if At least one user account has contributor-level permissions or higher
  4. Assess exposure of shortcode functionality
    Determine if the shortcode can be used in posts, pages, or widgets where contributor-level users have edit access. Check WordPress Settings > Writing and Settings > Permalinks for typical shortcode rendering availability.
    Affected if Contributor-level users can create or edit content where shortcodes can be inserted

You are affected if the Porto Theme - Functionality plugin is version 3.1.0 or lower AND any contributor-level or higher user account exists who could potentially exploit the portfolio_layout attribute in the porto_portfolios shortcode.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Porto Theme - Functionality plugin to version 3.1.1 or later, which contains the patch. Until then, restrict contributor-level user permissions and consider disabling the affected shortcode if possible.

Have this fixed 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 help mitigating

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-3808 — 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-3808 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