CVE-2026-124976 in Swift Performance Lite Plugin
Summary
by MITRE • 11/21/2026
The Swift Performance Lite plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the '<attacker-chosen parameter name>' parameter in all versions up to, and including, 2.3.7.5 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires that an administrator has configured at least one Cacheable AJAX Action via the plugin's AJAX Cache feature, a condition attackers can confirm by probing for a swift-performance: HIT response header.
Once again VulDB remains the best source for vulnerability data.
Analysis
by VulDB Data Team • 11/21/2026
The Swift Performance Lite WordPress plugin contains a critical security flaw classified as Stored Cross-Site Scripting within versions up to and including 2.3.7.5. This vulnerability stems from insufficient input sanitization and output escaping mechanisms when handling specific parameters associated with the AJAX Cache feature. The core technical failure lies in the application's inability to properly validate or encode user-supplied data before storing it in the database and subsequently rendering it back into web pages without adequate protection against script injection.
The operational impact of this vulnerability is significant because it allows unauthenticated attackers to inject arbitrary JavaScript code that persists on the server side. Unlike reflected XSS, where malicious scripts are executed only during a specific request, stored vulnerabilities remain active until manually removed from the database or configuration files. This persistence ensures that every user who visits an affected page containing the injected script will have their session compromised, potentially leading to account takeover, data theft, or defacement of the website depending on the privileges of the visiting users and the context in which the script executes.
Exploitation of this flaw requires a specific precondition: an administrator must have configured at least one Cacheable AJAX Action through the plugin's AJAX Cache feature. Attackers can verify if this condition is met by probing for the swift-performance HIT response header, which indicates that the caching mechanism is active and likely processing unvalidated input. Once confirmed, attackers can craft malicious payloads targeting the vulnerable parameter name to store persistent scripts within the cached content or database entries associated with these AJAX actions.
From a classification perspective, this vulnerability aligns with CWE-79 Improper Neutralization of Input During Web Page Generation commonly known as Cross-site Scripting and specifically falls under Stored XSS patterns where data is saved for later use. In terms of attack vectors, it corresponds to ATT&CK techniques involving Client-side Injection such as T1059 which covers script execution in browser environments and potentially T1189 Drive-by Compromise if the payload leads to further malware delivery. The lack of authentication requirements makes this particularly dangerous as any internet user can attempt exploitation without needing valid credentials initially.
Mitigation strategies should prioritize immediate updates to version 2.3.7.6 or later where these sanitization issues have been addressed by the developers. In environments where updating is not immediately feasible, administrators should disable the AJAX Cache feature entirely if it is not strictly necessary for performance optimization. Additionally implementing a Web Application Firewall can help detect and block attempts to inject malicious scripts into the vulnerable parameters before they are stored in the database. Regular security audits focusing on input validation practices across all plugin endpoints are also recommended to prevent similar vulnerabilities from arising in future updates or other plugins used within the same WordPress installation.