Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain author-level WordPress account
-
ExploitSubmit crafted value to vulnerable parameter
-
ExecutionInject SQL into unsanitized query
-
ImpactExfiltrate 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 | Requires an authenticated WordPress user holding the author role or higher on a site running Swift Performance Lite prior to 2.3.7.4; the plugin must be installed and active. Exploitation is limited by this authentication requirement - the attacker needs valid author-level (or higher) credentials, so it is not exploitable by anonymous visitors, which substantially narrows the realistic attacker population compared to a pre-auth flaw. No special non-default configuration is described; the vulnerable code path is the plugin's failure to sanitize/escape a value before use in a SQL statement. |
| Impact | This is a CWE-89 SQL injection in the Swift Performance Lite WordPress plugin (before 2.3.7.4) that requires an authenticated account with the author role or above. The provided CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N, 6.8) signals network reach with low complexity but meaningful privilege requirements. Note a discrepancy: the vector encodes PR:H, yet the description specifies 'author role and above,' which in WordPress is a low-privilege authenticated role - PR:L is more defensible, so treat the PR:H rating with skepticism. EPSS and SSVC data were not provided, and the vulnerability is not listed in CISA KEV, so there is no evidence of active exploitation. However, publicly available exploit code exists (WPScan). The net picture is a credentialed, not pre-auth, flaw: real but gated behind obtaining an author-level account, which limits mass exploitation and points toward opportunistic abuse on multi-author sites or post-compromise privilege leverage rather than widespread automated attacks. |
| Exploit ScenarioDerived | An attacker who holds (or phishes/registers into) a WordPress author-level account on a site running Swift Performance Lite below 2.3.7.4 submits a crafted value that is concatenated into a SQL statement without proper sanitization or escaping. Because publicly available exploit code exists (WPScan), the attacker can reliably extract sensitive database contents such as user credentials and secrets. The low attack complexity (AC:L) makes the injection straightforward once author access is held. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
SQL injection in Swift Performance Lite before 2.3.7.4 allows authenticated users with author-level or higher privileges to execute arbitrary SQL queries, potentially exposing sensitive database contents. The flaw arises from missing sanitization and escaping of a value used in a SQL statement (CWE-89), and publicly available exploit code exists. Exploitation requires a valid author account on a site with the plugin active, which narrows the attack surface compared to unauthenticated flaws.
RemediationAI
Update Swift Performance Lite to version 2.3.7.4 or later; the vendor has released a patch (Vendor-released patch: 2.3.7.4). Site administrators should apply this update promptly and verify the plugin version after upgrading. If immediate patching is not possible, restrict author-level and higher accounts to trusted users, review user roles for unnecessary privileges, and consider temporarily deactivating the plugin until the update can be applied-recognizing that deactivation may affect site performance features. Monitor the WPScan advisory (https://wpscan.com/vulnerability/5b24891e-1cd5-4ce8-9fc8-3c1392037e53/) and NVD entry for any updates.
Affected VersionsENISA
Affected Packages
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 Swift Performance Lite WordPress plugin fails to properly sanitize and escape a value before incorporating it into a SQL statement, leading to a CWE-89 SQL injection vulnerability. This class of flaw occurs when user-supplied input is concatenated into SQL queries without parameterization or escaping, allowing an attacker to alter query logic and extract arbitrary data from the WordPress database. The affected component is the plugin itself (CPE: cpe:2.3:a:unknown:swift_performance_lite:*:*:*:*:*:*:*:*), with all versions before 2.3.7.4 impacted. Exploitation requires an authenticated account with at least the author role, consistent with the assessed CVSS vector (PR:L) and the vendor's description; the vulnerability has a high confidentiality impact but no integrity or availability impact per the assessment.
Know when Swift Performance Lite 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
AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N
WordPress author is a low-privilege authenticated role so PR:L (not PR:H); SQLi reads database data giving C:H with no stated integrity/availability impact; same security authority so S:U.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
4DescriptionCVE.org
The Swift Performance Lite WordPress plugin before 2.3.7.4 does not properly sanitize and escape a value before using it in a SQL statement, which could allow users with the author role and above to perform SQL injection attacks.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
EUVD-2026-107070
GHSA-v5v6-jm3f-74w8
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB