Skip to main content

Porto Theme Functionality CVE-2026-42415

| EUVDEUVD-2026-93052 CRITICAL
SQL Injection (CWE-89)
2026-10-06 Patchstack GHSA-4wxh-r8p3-69rq
9.3
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Send crafted HTTP request to plugin endpoint
  2. Exploit
    Inject SQL via unsanitized parameter
  3. Execution
    Backend executes malicious query
  4. Impact
    Exfiltrate credentials and sensitive database contents

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

No authentication required (CVSS PR:N) - exploitable by remote unauthenticated attackers against any WordPress site with the Porto Theme Functionality plugin version 3.9.3 or earlier installed and active. The only practical prerequisite is that the vulnerable plugin is present and its affected endpoint is reachable over the network; no user interaction, special privileges, or non-default configuration is indicated by the description or vector. The primary limiting factor is simply upgrading past the vulnerable 3.9.3 build; the exact feature/parameter carrying the injection is not specified in the available data, so defenders cannot scope it to a single feature toggle.

Impact

This is a genuine priority for WordPress sites running the Porto theme's companion plugin, though several high-value signals are missing. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) describes the worst-practical combination for a web vulnerability - remote, low-complexity, unauthenticated, no user interaction - which aligns with the 'Unauthenticated SQL Injection' description and CWE-89, so the core signals are internally consistent. The 9.3 score is driven partly by the S:C (scope-changed) and A:L metrics chosen by Patchstack; the C:H/I:N confidentiality-dominant impact matches a data-disclosure SQLi, though I:N is slightly surprising for SQL injection and I treat it as conservative rather than authoritative. No EPSS score, no CISA KEV listing, and no public POC were provided in the input, so there is 'no public exploit identified at time of analysis' - the elevated risk here is structural (trivial-to-exploit unauthenticated SQLi in a widely-sold theme) rather than evidenced by observed exploitation. Unauthenticated SQLi flaws in popular WordPress ecosystem components are historically attractive for automated mass-scanning, so despite the absence of EPSS/KEV data the real-world risk should be treated as high and patched promptly.

Exploit ScenarioDerived

A remote attacker, without any account or credentials, sends a crafted HTTP request to a vulnerable endpoint exposed by the Porto Theme Functionality plugin (<= 3.9.3), injecting SQL through an unsanitized parameter. The injected query is executed against the WordPress database, allowing extraction of sensitive data such as user credentials, password hashes, and secret keys. No public exploit code was identified in the provided data, but the AV:N/AC:L/PR:N/UI:N profile means weaponization would be straightforward.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 06, 2026

Unauthenticated SQL injection in the Porto Theme Functionality WordPress plugin affects versions up to and including 3.9.3, allowing remote attackers to inject arbitrary SQL into the plugin's database queries without any prior authentication (CVSS vector PR:N, no user interaction). Successful exploitation can expose sensitive data stored in the site's WordPress database - the independent assessment rates confidentiality impact as High and integrity impact as Low, while the vendor/feed score of 9.3 assumes scope change and a different impact mix; both agree the issue is trivially network-reachable. There is no CISA KEV listing and no public exploit code identified at time of analysis, so this is a high-severity, easily reachable flaw rather than a confirmed actively exploited campaign, and no fixed plugin version is specified in the supplied advisory data.

RemediationAI

No vendor-released patch or fixed version is identified in the supplied data - the Patchstack advisory entry (https://patchstack.com/database/wordpress/plugin/porto-functionality/vulnerability/wordpress-porto-theme-functionality-plugin-3-9-3-sql-injection-vulnerability) is the only reference and does not specify a patched build, so the first action is to check the plugin's availability for an update beyond 3.9.3 and to contact the vendor (p-themes) or monitor the Patchstack record for a fixed version before assuming one exists. Until a patched release is confirmed, the highest-confidence mitigation is to deactivate and remove the Porto Theme - Functionality plugin; the trade-off is that this is a companion plugin for the Porto theme, so theme features, shortcodes, and page-builder elements it provides will break or degrade, and the impact on the live site must be tested on staging first. Where the plugin cannot be removed, deploy a virtual patch at the WAF/reverse-proxy layer using SQL-injection signature rules applied to requests targeting the plugin's endpoints and admin-ajax.php actions, accepting that signature coverage is imperfect and that the undisclosed injection parameter means the rule may not be complete. Additional compensating controls include restricting access to any plugin-specific REST/AJAX endpoints, rate-limiting and closely reviewing request logs for SQL metacharacter payloads, and, because the flaw is unauthenticated, treating any traffic to the vulnerable route as potentially hostile; none of these eliminate the root cause, and the plugin should be upgraded to the first confirmed patched version as soon as the vendor publishes one.

Affected VersionsENISA

Porto Theme - Functionality n/a ≤3.9.3

Affected Packages

euvd porto_theme_functionality no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The affected component is a WordPress plugin, Porto Theme - Functionality (CPE cpe:2.3:a:p-themes:porto_theme_-_functionality), which ships as the companion/feature plugin for the Porto WordPress theme and is therefore present on a large population of commercial-theme sites. The root cause is CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), meaning user-controllable input reaches a SQL statement without adequate parameterization - typically a WordPress plugin query built through the global $wpdb object without $wpdb->prepare() or with unsanitized values interpolated directly into the SQL string. The CVSS:3.1 vector AV:N/AC:L/PR:N/UI:N confirms the classic shape of this bug class: the vulnerable endpoint is reachable over HTTP with no authentication, no privileges, and no victim interaction, so exploitation requires only a crafted request. The exact vulnerable function, parameter, or shortcode/AJAX route is not disclosed in the available data, which limits defenders' ability to scope or fingerprint the injection point. Note the scoring divergence: the published score (9.3, S:C/C:H/I:N/A:L) assumes a scope change and no integrity impact, while the independent assessment (8.7-equivalent shape: S:U/C:H/I:L/A:N) treats the database as the same security authority and allows for limited integrity impact - the practical takeaway (unauthenticated, remotely reachable, high confidentiality loss) is consistent across both.

Know when Wordpress Plugin gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 9.3 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L
vuln.today AI 8.2 HIGH

Remote unauthenticated SQLi with no user interaction gives AV:N/AC:L/PR:N/UI:N; database read yields C:H, limited write potential I:L, and I keep S:U absent evidence of impact beyond the DB.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

DescriptionCVE.org

Unauthenticated SQL Injection in Porto Theme - Functionality <= 3.9.3 versions.

Executive ViewAI

Why It Matters

The Porto Theme Functionality WordPress plugin, in versions up to and including 3.9.3, exposes public-facing websites to a critical unauthenticated database injection flaw that could allow attackers to read sensitive information from the site’s WordPress database. Organizations relying on this plugin for customer-facing or business-critical sites face potential privacy, regulatory, and reputational harm, especially because no vendor patch is currently available. Leadership should prioritize immediate exposure reduction and interim monitoring while a fixed release is pursued.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include deactivating or removing the Porto Theme Functionality plugin on versions up to and including 3.9.3, deploying WAF rules to block SQL injection attempts against plugin endpoints, restricting database access, monitoring web and database logs, and rotating database credentials and WordPress salts if compromise is suspected.

Threat Intelligence Overview

EPSS Score
0.2%
Top 85% exploitable
Prevalence
Medium
companion plugin for a popular commercial WordPress theme, not everywhere
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +46
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

CVE-2023-6553 CRITICAL POC
9.8 Dec 15

The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1

CVE-2024-5084 CRITICAL POC
9.8 May 23

The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil

CVE-2024-44000 CRITICAL POC
9.8 Oct 20

Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote

CVE-2020-36847 CRITICAL POC
9.8 Jul 12

The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner

CVE-2025-27007 CRITICAL POC
9.8 May 01

The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut

CVE-2016-1209 CRITICAL POC
9.8 May 14

The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via

CVE-2024-4443 CRITICAL POC
9.8 May 22

The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based

CVE-2024-1698 CRITICAL POC
9.8 Feb 27

SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a

CVE-2023-6875 CRITICAL POC
9.8 Jan 11

The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i

CVE-2024-1512 CRITICAL POC
9.8 Feb 17

The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base

CVE-2024-4295 CRITICAL POC
9.8 Jun 05

The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in

CVE-2024-50498 CRITICAL POC
10.0 Oct 28

Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy