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

CVE-2019-11507 Scanner

CVE-2019-11507 Scanner - Cross-Site Scripting (XSS) vulnerability in Pulse Secure Pulse Connect Secure

Est. Time~10 seconds
Scan TypeSingle Scan
Targetsdomain, subdomain, ipv4
CostFree
2.5k
Times Used
continuous scan runs
4.4k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
CVECVE-2019-11507
6.1
CVSSmedium
Exploitable remotely over the internet · no authentication required · user interaction needed.

In Pulse Secure Pulse Connect Secure (PCS) 8.3.x before 8.3R7.1 and 9.0.x before 9.0R3, an XSS issue has been found on the Application Launcher page.

Attack Vector
Network
Privileges Req.
None
User Interaction
Required
Affected
n/aby n/a
n/a
Updated Aug 21, 2026View on NVD →
Detail

Pulse Secure Pulse Connect Secure is widely used in corporate environments for secure remote access and VPN connectivity. It is primarily deployed by IT administrators to allow employees secure and encrypted connections to corporate networks from external locations. The software is trusted for its advanced network protection features and plays a crucial role in protecting sensitive corporate data from unauthorized internet access. Its user-friendly interface and robust security features make it a popular choice for companies looking to maintain high levels of security without compromising ease of access for authorized users. The software is regularly updated to address any emerging vulnerabilities, ensuring continuous protection against potential threats. Given the increasing reliance on remote work, tools like Pulse Connect Secure have become essential in maintaining seamless and secure remote connectivity.

The Cross-Site Scripting (XSS) vulnerability in Pulse Secure Pulse Connect Secure allows attackers to inject malicious scripts into web pages viewed by other users. These scripts can execute in the victim's browser, potentially enabling attackers to hijack user sessions or conduct phishing attacks. The vulnerability is specifically due to insufficient input sanitization on the application launcher page. Attackers can exploit this by tricking users into clicking on a crafted link, resulting in the execution of the malicious script in the context of the affected page. This type of vulnerability is commonly exploited in drive-by attacks, where users unknowingly execute scripts simply by visiting a malicious site. XSS is a serious issue because it undermines users' trust in the web application and can have wide-ranging consequences for user security.

The technical details of the vulnerability involve the failure to properly sanitize inputs to the application launcher page. Malicious actors can craft a URL containing a harmful script embedded within an element or similar tags that exploit this weakness. When a user accesses this URL, the poorly sanitized input allows the script to execute within their browser session. The XSS vulnerability bypasses same-origin policy protections, which would typically block the execution of unauthorized scripts. By carefully embedding harmful scripts in URLs, attackers are capable of exploiting this oversight without requiring further interaction from users, aside from visiting a compromised link. The template tests for this vulnerability by sending crafted GET and POST requests to a set of specific endpoints and evaluating the resulting HTTP responses for indications of a successful XSS attack.

If this vulnerability is exploited, attackers can perform a variety of malicious activities. Users may unknowingly execute scripts that steal cookies, session tokens, or other sensitive information, potentially compromising user accounts and leading to unauthorized access. Additionally, attackers could manipulate content on affected pages, defacing applications or redirecting users to phishing pages. Over time, successful exploitation could degrade user trust and impact the integrity of the affected service, causing reputational and financial harm to the organization. The unchecked execution of scripts might also provide a foothold for attackers to initiate further attacks within the network environment, exploiting additional vulnerabilities.

REFERENCES

Solution Advice
  • Update Pulse Secure Pulse Connect Secure to version 8.3R7.1 or 9.0R3 or later.
  • Implement web application firewalls to detect and block XSS payloads.
  • Conduct regular security audits and code reviews to catch vulnerabilities early.
  • Ensure all user inputs are properly sanitized and encoded before execution in a browser.
  • Consider using Content Security Policy (CSP) headers to mitigate the impact of XSS attacks.

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.

CVE-2019-11507 Scanner - Cross-Site Scripting (XSS) vulnerability in Pulse Secure Pulse Connect Secure | S4E