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

CVE-2024-3807

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 for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 7.1.0 via 'porto_page_header_shortcode_type', 'slideshow_type' and 'post_layout' post meta. 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. This was partially patched in version 7.1.0 and fully patched in version 7.1.1.

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 WordPress theme versions up to 7.1.0 contain a Local File Inclusion vulnerability in the handling of post meta fields 'porto_page_header_shortcode_type', 'slideshow_type', and 'post_layout'. Authenticated attackers with contributor-level or higher permissions can manipulate these meta parameters to include and execute arbitrary server files, leading to PHP code execution. This allows attackers to bypass access controls and achieve remote code execution.

MitigationUpdate the Porto theme to version 7.1.1 or later. If immediate patching is not feasible, restrict contributor-level user permissions and audit existing user accounts with contributor access.

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 installation and version
    In WordPress admin, go to Appearance > Themes to see the active theme version. Alternatively, check the style.css file in wp-content/themes/porto/ for the 'Version' header.
    Affected if Porto theme is installed and version is 7.1.0 or lower (any version up to and including 7.1.0)
  2. Confirm the vulnerability applies to this installation
    The flaw requires the site to allow contributor-level or higher user accounts. Check Users > All Users in wp-admin to list accounts with contributor, author, editor, or administrator roles.
    Affected if Any user account with contributor-level or higher permissions exists on the site (these roles can exploit the vulnerability)
  3. Identify the vulnerable meta fields in use
    Query the wp_postmeta table for the meta keys 'porto_page_header_shortcode_type', 'slideshow_type', and 'post_layout' using: SELECT * FROM wp_postmeta WHERE meta_key IN ('porto_page_header_shortcode_type', 'slideshow_type', 'post_layout');
    Affected if These meta fields exist in the database (the LFI can be triggered via posts/pages using these meta values)
  4. Check for recent unauthorized user accounts
    Audit user registration dates and activity logs, particularly for contributor-level accounts created recently or showing unusual meta modifications.
    Affected if Contributor or higher accounts exist that were created without admin authorization or show suspicious activity

You are affected if the Porto theme version is 7.1.0 or lower AND at least one contributor-level or higher user account exists 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Porto theme to version 7.1.1 or later. If immediate patching is not feasible, restrict contributor-level user permissions and audit existing user accounts with contributor access.

Recommended fix High confidence

Porto theme version 7.1.1

  1. Backup your WordPress site before making any changes
  2. Navigate to Appearance > Themes in the WordPress admin dashboard
  3. Locate the Porto theme and check the current version is below 7.1.1
  4. Update the Porto theme to version 7.1.1 or later
  5. Verify the update was successful by checking the theme version in Appearance > Themes
  6. Review user accounts with contributor-level and above permissions to ensure no unauthorized access occurred

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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