WordPress security by component
Porto Theme - Functionality
Plugin description
Porto Theme - Functionality is a WordPress component with 4 published CVE records in this archive. The latest tracked vulnerability was published Dec 09, 2025; the highest CVE/CNA score is 9.3.
Plugin slug:
porto-functionalityLatest vulnerability
CVE-2025-63067: Porto Theme - Functionality: A security weakness
Porto Theme - Functionality is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
| Safe version |
|
||
|---|---|---|---|
| Dec 09, 2025 |
CVE-2025-63067
Porto Theme - Functionality: A security weakness
Porto Theme - Functionality is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE4.3
NVDPending
|
| Dec 09, 2025 |
CVE-2025-63066
Porto Theme - Functionality: Cross-site scripting
Porto Theme - Functionality is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE6.5
NVDPending
|
| Jan 02, 2025 |
CVE-2023-48739
Porto Theme - Functionality: A security weakness
Porto Theme - Functionality is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE5.3
NVDPending
|
| Dec 19, 2023 |
CVE-2023-48738
Porto Theme - Functionality: SQL injection
Porto Theme - Functionality is affected by SQL injection. Exposure depends on how the affected operation is made reachable by the site. A successful request can alter database queries and expose or modify WordPress data.
|
See mitigation notes |
CVE9.3
NVD9.8
|