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

CVE-2024-3806

CRITICAL · 9.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 →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 the 'porto_ajax_posts' function. This makes it possible for unauthenticated attackers 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 WordPress theme versions up to 7.1.0 contain a Local File Inclusion vulnerability in the 'porto_ajax_posts' function, allowing unauthenticated attackers to include arbitrary files from the server and execute them as PHP code, achieving remote code execution.

MitigationUpdate the Porto theme to version 7.1.1 or later immediately. If updating is not immediately feasible, disable the 'porto_ajax_posts' functionality through web server rules or temporarily deactivate the theme.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 the installed Porto theme version
    Navigate to the WordPress admin dashboard, go to Appearance > Themes, and locate the Porto theme to view its current version number
    Affected if The installed version is 7.1.0 or any earlier version (versions up to and including 7.1.0 are affected)
  2. Verify the theme version via filesystem
    Access the theme files via FTP or file manager and locate the style.css file in the /wp-content/themes/porto/ directory; read the version header from the file
    Affected if The version listed in the style.css file header is 7.1.0 or lower
  3. Check if the vulnerable endpoint is accessible
    Test whether the 'porto_ajax_posts' AJAX endpoint is exposed by making a request to /wp-admin/admin-ajax.php?action=porto_ajax_posts (or via front-end AJAX calls if the theme exposes this action publicly)
    Affected if The endpoint responds and accepts parameters without authentication, indicating the functionality is enabled and reachable
  4. Inspect server access logs for exploitation attempts
    Review web server access logs (Apache/nginx) for requests containing 'action=porto_ajax_posts' combined with 'file=' or 'template=' parameters that may indicate LFI exploitation attempts
    Affected if Unusual or unauthorized requests to the porto_ajax_posts action with file inclusion parameters are found in the logs

You are affected if the installed Porto theme version is 7.1.0 or earlier AND the porto_ajax_posts functionality is accessible without authentication.

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 immediately. If updating is not immediately feasible, disable the 'porto_ajax_posts' functionality through web server rules or temporarily deactivate the theme.

Recommended fix Moderate confidence

Any version newer than 7.1.0 (check ThemeForest or WordPress theme repository for the latest stable release)

  1. Update the Porto theme to the latest available version from the WordPress theme repository or ThemeForest
  2. Navigate to Dashboard > Appearance > Themes in WordPress admin
  3. If a newer version is available, click 'Update Now' on the Porto theme
  4. Alternatively, download the latest version from the theme vendor and upload via WordPress admin or FTP
  5. Verify the updated version is above 7.1.0
Caveat Review theme changelog for potential child theme or customization impacts before updating

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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