WP Fusion Lite <= 3.37.18 Reflected Cross-Site Scripting
Description
The WP Fusion Lite plugin (≤ 3.37.18) suffers from reflected XSS via the startdate parameter in the log table list, letting attackers inject arbitrary scripts.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
The WP Fusion Lite plugin (≤ 3.37.18) suffers from reflected XSS via the `startdate` parameter in the log table list, letting attackers inject arbitrary scripts.
Vulnerability
The WP Fusion Lite WordPress plugin, in versions up to and including 3.37.18, contains a reflected cross-site scripting (XSS) vulnerability in the ~/includes/admin/logging/class-log-table-list.php file. The startdate parameter is not properly sanitized or escaped before being output in the log table list page, allowing injection of arbitrary web scripts [1][2].
Exploitation
An attacker can send a crafted URL with a malicious startdate parameter to a logged-in WordPress administrator. No authentication or special privileges are required to trigger the reflected XSS; the victim need only click the crafted link. The vulnerable code path is reachable when the administrator views the log table under the WP Fusion settings [1][2].
Impact
Successful exploitation allows the attacker to inject arbitrary JavaScript or HTML into the victim's browser in the context of the WordPress admin dashboard. This can lead to session hijacking, credential theft, or performing administrative actions on behalf of the victim [1][2].
Mitigation
The vendor released a patched version of WP Fusion Lite after 3.37.18. Users should upgrade to the latest version, which sanitizes the startdate parameter appropriately [1]. As an interim workaround, administrators can avoid clicking on untrusted links while logged in [1][2].
AI Insight generated on May 25, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2- Range: <=3.37.18
- Range: 3.37.18
Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
2- plugins.trac.wordpress.org/browser/wp-fusion-lite/trunk/includes/admin/logging/class-log-table-list.phpmitrex_refsource_MISC
- www.wordfence.com/vulnerability-advisories/mitrex_refsource_MISC
News mentions
0No linked articles in our index yet.