The vulnerability identified as CVE-2026-22704 affects the PSU HAX CMS, a content management system designed for microsite management using PHP or NodeJs backends. Specifically, this vulnerability allows stored cross-site scripting (XSS) in versions 11.0.6 to before 25.0.0. If exploited, it could lead to account takeover, posing significant risks to organizations utilizing this platform.
The CVSS score for this vulnerability is 8, categorizing it as high severity, which underscores the potential impact on confidentiality, integrity, and availability. Given its nature, organizations must recognize the urgency to address this issue promptly.
As of the most recent update, this vulnerability has been confirmed to have an exploit available, adding to the urgency for defenders. Organizations should prioritize patching immediately to mitigate the risks associated with this vulnerability.
The patch for this vulnerability has been made available in version 25.0.0. Organizations that have not yet updated their systems should do so as part of their immediate response to this vulnerability.
Vulnerability Details
HAX CMS helps manage microsite universe with PHP or NodeJs backends. In versions 11.0.6 to before 25.0.0, HAX CMS is vulnerable to stored XSS, which could lead to account takeover. This issue has been patched in version 25.0.0.
The vulnerability is classified under CWE-79, which pertains to improper neutralization of input during web page generation ('Cross-site Scripting'). The CVSS vector for the vulnerability indicates an attack vector of 'NETWORK', with a high attack complexity, requiring low privileges and user interaction.
Technical Analysis
The root cause of this vulnerability lies in the way the application processes and renders user inputs without proper sanitization. Attackers can exploit this by injecting malicious scripts that are stored and executed in the context of users' browsers, leading to unauthorized actions on behalf of the user.
The attack vector is network-based, meaning that attackers can exploit the vulnerability remotely without needing physical access to the system. The complexity of the attack is considered high, as it requires users to interact with the malicious payload, such as clicking on a link or submitting a form.
Privileges required are low, allowing even unauthenticated users to exploit the vulnerability, which significantly increases the risk to organizations. User interaction is required, which means the attacker needs to trick the user into performing an action that executes the malicious script.
The impact of this vulnerability is severe, with potential consequences on confidentiality, integrity, and availability, as sensitive data can be accessed and manipulated by attackers.
Risk & Impact Analysis
Risk to organizations includes the potential for data breaches, unauthorized access to user accounts, and significant reputational damage. The stored XSS vulnerability could allow attackers to perform actions as legitimate users, compromising both user data and organizational integrity.
With the increasing sophistication of cyber threats, the urgency for organizations to patch this vulnerability cannot be overstated. Organizations should address this in their priority patch cycle, ensuring that all affected systems are updated to version 25.0.0 or later.
The EPSS score of 0.00076 reflects a low probability of exploitation in the wild; however, the presence of an exploit in exploit databases indicates that organizations should not underestimate the risk. Continuous monitoring and immediate remediation are essential.
Exploitation Status
Signal | Status |
|---|---|
Known Exploit | Yes |
Public PoC | No |
Actively Exploited | No |
Ransomware Use | No |
Affected Versions
This vulnerability affects HAX CMS versions 11.0.6 to before 25.0.0. Organizations should upgrade to version 25.0.0 or later to mitigate the risk.
Mitigation & Remediation
Organizations should patch their systems to version 25.0.0 of HAX CMS immediately to eliminate this vulnerability. If patching is not immediately feasible, organizations should consider implementing input validation and sanitization measures to defend against XSS attacks. Additionally, restricting access to sensitive areas of the application and monitoring user activity can help mitigate the risk.
For further guidance on security testing, organizations can explore our services on penetration testing and other related assessments.
Detection Guidance
Organizations should monitor logs for unusual activity indicating potential XSS attacks. This includes tracking login attempts and any unexpected changes to user account settings. Behavioral anomalies, such as multiple failed login attempts followed by a successful one, could indicate exploitation attempts.
Network signatures for known exploit patterns should be integrated into intrusion detection systems to alert on suspicious traffic. Additionally, any changes to the application that don't align with standard operational procedures should be investigated.
AppSecure Threat Intelligence Insight
CVE-2026-22704 represents a significant threat to organizations using HAX CMS. The existence of an exploit indicates that attackers are actively seeking to exploit this vulnerability. Security teams should adopt a proactive approach to vulnerability management, ensuring that systems are regularly updated and patched.
This incident highlights the importance of robust application security practices, including regular security assessments. For teams looking to enhance their security posture, we recommend reviewing our guide on penetration testing methodology and engaging in continuous security testing to identify potential weaknesses before they can be exploited.
Organizations should also be aware of the evolving threat landscape and consider investing in vulnerability management programs to ensure they stay ahead of potential threats. Lastly, fostering a culture of security awareness among employees can help prevent social engineering attacks that often accompany technical vulnerabilities.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

.webp)