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 Jul 25, 2025

CVE-2025-34141 Scanner

CVE-2025-34141 Scanner - Cross-Site Scripting (XSS) vulnerability in ETQ Reliance

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-2025-34141
5.1
CVSSmedium
Exploitable remotely over the internet · no authentication required.

A reflected cross-site scripting (XSS) vulnerability exists in ETQ Reliance CG (legacy) platform within the `SQLConverterServlet` component. This vulnerability requires user interaction, such as clicking a crafted link, and may result in execution of unauthorized scripts in the user's context. The affected servlet was unnecessarily exposed to authenticated users and has since been disabled in version SE.2025.1.

Attack Vector
Network
Privileges Req.
None
User Interaction
A
Affected
Reliance CG (legacy)by ETQ
AFFECTED< SE.2025.1SAFE ✓≥ SE.2025.1
Updated Aug 22, 2026View on NVD →
Detail

ETQ Reliance is widely utilized by organizations for managing compliance and quality processes, providing tools for document control, training management, and audits. It serves numerous industries including life sciences, electronics, and manufacturing due to its robust platform supporting regulatory compliance. Users leverage ETQ Reliance for its configurability, enabling tailored solutions to meet specific organizational needs. Accessing ETQ Reliance requires authentication, which ensures that sensitive data and workflows are protected. Over the years, ETQ Reliance has evolved, adding features and improving security to safeguard user operations. Regular updates and patches are applied to mitigate vulnerabilities and stay compliant with industry standards.

The vulnerability detected, a reflected cross-site scripting (XSS), allows an attacker to inject malicious scripts that execute within a user's session. This type of vulnerability usually requires user interaction, such as clicking on a crafted URL. When the script is executed, it exploits the trust relationship within the authenticated session of the user accessing ETQ Reliance. XSS vulnerabilities like this pose risks to data confidentiality, session integrity, and user privacy. The exposure primarily lies within the SQLConverterServlet component, which was not adequately secured against such injections. Patching and proactive measures are necessary to close this security gap effectively.

Technical details reveal that the vulnerable endpoint is the SQLConverterServlet, which allows for crafted payloads like `MySQLStm`, containing HTML/JavaScript injection that is reflected back to the user's browser. This servlet endpoint was unnecessarily exposed to authenticated users due to improper validation measures. Attackers could exploit this by sending specially constructed URLs that inject scripts into the browser context of an authenticated user. This reflects the vulnerability through response data that fails to correctly sanitize input before reflecting it back to the client-side context. Such vulnerabilities leverage user interaction as a vector for executing malicious actions, usually requiring little more than a click.

The exploitation of this vulnerability can lead to session hijacking, where an attacker steals or manipulates a user's session in real-time. Unauthorized actions could be performed by the attacker, such as exfiltrating sensitive data like authentication cookies or deploying further attacks on the organization's network. The repercussions of an XSS attack extend to damaging user trust and compromising the overall integrity of the application. Organizations must be vigilant in applying patches and enhancing frontend security to mitigate these risks.

REFERENCES

Solution Advice
  • Upgrade to ETQ Reliance version SE.2025.1 or later to ensure the vulnerable SQLConverterServlet component is disabled.
  • Implement input validation and output encoding to prevent reflection or injection of script tags in user interactions.
  • Utilize Content Security Policy (CSP) headers to restrict the execution of untrusted scripts on user browsers.
  • Conduct regular security audits and code reviews to identify and patch similar vulnerabilities proactively.
  • Educate users on recognizing potential phishing and crafted link attacks to mitigate user-interaction-based threats.

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.