WordPress theme
Porto security & vulnerabilities
Unpatched vulnerability in the latest version
At least one vulnerability affects the latest version and no fix has been released. Deactivate the theme or restrict access to the affected feature until the vendor ships a patch.
- Critical1
- High1
- Medium1
- Low0
All Porto vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium6.1 | Reflected Cross-Site Scripting ≤7.6.2No patch available | CVE-2026-28075 | |
| High8.8 | Authenticated (Contributor+) Local File Inclusion via Post Meta ≤7.1.0Update to 7.1.1 | CVE-2024-3807 | |
| Critical9.8 | Unauthenticated Local File Inclusion via porto_ajax_posts ≤7.1.0Update to 7.1.1 | CVE-2024-3806 |
- Medium6.1Reflected Cross-Site Scripting
≤7.6.2No patch available
- High8.8Authenticated (Contributor+) Local File Inclusion via Post Meta
≤7.1.0Update to 7.1.1
- Critical9.8Unauthenticated Local File Inclusion via porto_ajax_posts
≤7.1.0Update to 7.1.1
Porto: common questions
Does Porto have known vulnerabilities?
Yes. VulnCrest Radar lists 3 known vulnerabilities in Porto: 1 critical, 1 high, 1 medium. At least one is not fixed in the latest version.
How do I check which version of Porto I run?
In wp-admin open Appearance → Themes and select the theme; the version is shown under the name. Without admin access, our passive Check my site tool can often read it from public files.
What is the most recent Porto vulnerability?
CVE-2026-28075, published Feb 27, 2026: Porto <= 7.6.2 - Reflected Cross-Site Scripting. Severity: Medium (CVSS 6.1).
Is any Porto vulnerability listed in CISA KEV?
No. None of the known Porto vulnerabilities is currently listed in the CISA KEV catalog.