S4E just found a high-severity finding from top 10 tcp port service scan
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
high·Product Based Web Vulnerabilities·Updated Feb 11, 2026

CVE-2024-13094 Scanner

This scanner targets the trigger creation endpoint in WP Triggers Lite, where unsanitized input allows stored XSS, enabling attackers to execute arbitrary JavaScript in admin sessions.

Est. Time~10 seconds
Scan TypeSingle Scan
Targetsdomain, subdomain, ipv4
CostFree
3.4k
Times Used
continuous scan runs
5.9k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
CVECVE-2024-13094
7.1
CVSShigh
Exploitable remotely over the internet · no authentication required · user interaction needed.

The WP Triggers Lite WordPress plugin through 2.5.3 does not sanitise and escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin.

Attack Vector
Network
Privileges Req.
None
User Interaction
Required
Affected
WP Triggers Lite
0
Updated Aug 22, 2026View on NVD →
Detail

WP Triggers Lite is a popular WordPress plugin used by site administrators and developers to create dynamic, condition-based triggers that enhance user interactivity and engagement. It integrates seamlessly with various themes and content management systems, making it a versatile tool for small to medium-sized businesses aiming to improve their website's responsiveness and functionality.

The vulnerability identified is a Cross-Site Scripting (XSS) flaw, a common web security issue arising from inadequate input sanitization. In WP Triggers Lite version 2.5.3, this flaw allows attackers to inject malicious scripts into web pages, which can then be executed in the context of other users' browsers, leading to unauthorized actions and data exposure.

Specifically, the vulnerability exists in the trigger creation endpoint where user-supplied data is not properly sanitized before being stored and later rendered. An attacker can craft a malicious trigger name or description containing JavaScript code, which will execute when an administrator views the triggers list or settings page, bypassing standard security controls.

If exploited, an attacker could steal session cookies, perform actions on behalf of an admin (like creating new admin accounts), deface the site, or redirect users to malicious sites. This can lead to complete site compromise, data theft, and loss of user trust, making immediate remediation critical.

Solution Advice
  • Update WP Triggers Lite to version 2.5.4 or later, which includes a patch for CVE-2024-13094.
  • Implement strict input validation and output escaping for all user-supplied data, especially in trigger creation fields.
  • Apply a Web Application Firewall (WAF) with XSS detection rules to block malicious payloads.
  • Regularly audit all WordPress plugins for known vulnerabilities using automated scanners.
  • Enforce Content Security Policy (CSP) headers to restrict script execution sources.
  • Educate administrators on the risks of XSS and safe browsing practices.
  • Consider using a security plugin that provides real-time monitoring and alerts for suspicious activities.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

11,000+ scanners. Free to start. No credit card required.