CVE-2024-3808 HIGH

CVE-2024-3808: Porto Theme - Functionality <= 3.1.0 - Authenticated (Contributor+) Local File Inclusion via Shortcode

Vendor P-Themes
Product Porto Theme - Functionality
Weakness CWE-98 · PHP file inclusion
Published May 9, 2024
Last update April 8, 2026

CVSS base score

8.8/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality High
Integrity High

CVSS vector

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

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

The Porto Theme for WordPress contains a vulnerability that allows authenticated users with low privileges to read sensitive data, modify site content, and disrupt service. The flaw stems from improper input validation in the theme's functionality. An attacker with a basic user account can exploit this remotely without user interaction. Sites running Porto Theme version 3.1.0 or earlier are affected.

What an attacker can do

03Attacker Capabilities

Read sensitive data, modify site content, and cause service disruption with a low-privilege user account.

Potential impact on your site

04Site Impact

Compromised data confidentiality, site content integrity, and availability for all users of Porto Theme 3.1.0 or earlier.

Conditions required to exploit

05Prerequisites

Attacker needs a valid low-privilege user account on the site; no user interaction required.

Key dates

06Disclosure timeline

May 9, 2024 CVE published
April 8, 2026 Record updated