CVE-2026-6371: Stored XSS in Limatek LimRAD NAC – Patch Version 5.5.7.3.9
Limatek System Inc.'s LimRAD NAC product contains a stored cross-site scripting (XSS) vulnerability that allows an authenticated attacker with limited network access to inject malicious scripts into the web interface. These scripts persist in the system and execute in the browsers of other users who view affected pages, potentially compromising session integrity and enabling unauthorized actions within the NAC application.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 4.8 MEDIUM · CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
- Weaknesses (CWE)
- CWE-79
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-07-08 / 2026-07-20
NVD description (verbatim)
Improper neutralization of input during web page generation ('cross-site scripting') vulnerability in Limatek System Inc. LimRAD NAC allows Stored XSS. This issue affects LimRAD NAC: before 5.5.7.3.9.
1 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-6371 is a stored XSS vulnerability (CWE-79) in LimRAD NAC versions before 5.5.7.3.9. The vulnerability stems from improper input sanitization during web page generation. An attacker with local network access and valid credentials can inject JavaScript payloads that are stored server-side and reflected to subsequent users. The attack vector is adjacent network (AV:A), requires low complexity (AC:L), needs low privilege access (PR:L), and depends on user interaction (UI:R). The impact is limited to confidentiality and integrity compromise with no availability impact, reflected in the CVSS 3.1 score of 4.8 (MEDIUM severity).
Business impact
Stored XSS in a network access control appliance creates operational risk by potentially allowing attackers to escalate privileges, steal administrative session tokens, redirect users to malicious sites, or deface the management interface. Since NAC systems control network access policies and device onboarding, compromise could undermine the entire network segmentation strategy. Organizations relying on LimRAD for access enforcement should treat this as a control-plane integrity issue requiring prompt remediation.
Affected systems
Limatek System Inc. LimRAD NAC versions prior to 5.5.7.3.9 are affected. Organizations running LimRAD as their network access control solution should audit their deployment version immediately. No other vendors or products are listed as affected by this specific vulnerability.
Exploitability
Exploitation requires an attacker to already possess valid credentials and be on the same network segment as the LimRAD appliance (adjacent network access). This substantially lowers real-world risk in well-segmented environments but remains concerning in shared network scenarios or for insider threats. The need for user interaction means the attacker must either trick an administrator into viewing a malicious page or wait for routine administrative access. There is no evidence this vulnerability is being actively exploited in the wild, and it has not been added to the CISA Known Exploited Vulnerabilities catalog.
Remediation
Upgrade LimRAD NAC to version 5.5.7.3.9 or later. Organizations unable to patch immediately should restrict administrative access to the LimRAD web interface to trusted networks, disable unnecessary user accounts, and enforce strong authentication. Consider deploying Web Application Firewall (WAF) rules to block common XSS payloads if direct patching is delayed.
Patch guidance
Verify the current version of your LimRAD NAC deployment via the administrator console or system configuration page. Limatek System Inc. should provide patched builds at version 5.5.7.3.9 or above. Consult the vendor's official advisory for upgrade procedures, as network access control appliances typically require coordinated maintenance windows. Test patches in a non-production environment before deployment to ensure compatibility with your network policies and device workflows.
Detection guidance
Monitor LimRAD web server logs for unusual characters or script tags in HTTP request parameters and POST bodies (e.g., <script>, onerror=, javascript:). Review the activity logs for administrative accounts making changes to web content or user interface templates. Inspect the browser console of the LimRAD management interface for unexpected JavaScript errors or console warnings that may indicate injected code. Organizations with SIEM integration can create alerts for HTTP requests containing common XSS vectors submitted to the LimRAD appliance.
Why prioritize this
Although the CVSS score is MEDIUM (4.8), prioritize this vulnerability if LimRAD is internet-facing or accessible from untrusted network segments, or if you have high-privilege administrative accounts that could be compromised. If LimRAD is strictly isolated to a trusted administrative network with strong access controls, prioritize it after critical and high-severity vulnerabilities affecting your external-facing systems. The stored nature of the XSS means it poses persistent risk once injected.
Risk score, explained
The CVSS 3.1 score of 4.8 reflects the restricted attack vector (adjacent network only, not network-wide), requirement for prior authentication, low-complexity exploitation, and limited scope of impact. Confidentiality and integrity are partially compromised, but availability remains unaffected. In isolated network environments, this score appropriately reflects low urgency; however, organizations with less mature network segmentation should consider the risk higher in practice.
Frequently asked questions
Can this vulnerability be exploited remotely over the internet?
No. The attack vector is adjacent network (AV:A), meaning the attacker must be on the same local network segment or have network-layer access to the LimRAD appliance. Remote exploitation is not possible unless LimRAD is exposed on a public IP address, in which case the risk profile increases significantly.
Do I need valid LimRAD credentials to exploit this vulnerability?
Yes. The vulnerability requires low-privilege authenticated access (PR:L). An attacker must have a valid user account on the LimRAD system, though they do not require administrative rights to inject the stored XSS payload.
What is the difference between stored and reflected XSS, and why does it matter here?
Stored XSS persists on the server and affects all users who subsequently view the compromised page, making it a broader threat. Reflected XSS only affects the attacker's immediate victim through a crafted URL. This vulnerability is stored, meaning once injected, it continues to pose risk until removed, justifying urgent patching.
Is there a CISA advisory or active exploit code for this vulnerability?
As of the latest data, this vulnerability has not been added to CISA's Known Exploited Vulnerabilities (KEV) catalog and has not been widely exploited in the wild. However, the lack of public exploitation does not mean you should delay patching—apply updates according to your risk assessment and maintenance schedule.
This analysis is provided for informational purposes and reflects publicly available vulnerability data as of the publication date. SEC.co makes no warranty regarding patch availability, vendor timelines, or the completeness of affected product lists. Organizations should verify patch status directly with Limatek System Inc. and conduct internal testing before deployment. The absence of a vulnerability from the CISA KEV catalog does not guarantee it is not being exploited; conduct threat intelligence research specific to your environment. This document does not constitute legal or compliance advice; consult your security and legal teams regarding remediation obligations. Source: NVD (public-domain), retrieved 2026-08-17. Analysis generated by SEC.co (claude-haiku-4-5).
Weaknesses (CWE)
Related vulnerabilities
- CVE-2016-20070MEDIUMPrivilege Escalation & Stored XSS in WordPress Booking Calendar Contact Form 1.0.23
- CVE-2018-25384MEDIUMStored XSS in Wikidforum 2.20 Allows Authenticated Attackers to Inject Malicious Scripts
- CVE-2019-25731MEDIUMStored XSS in Zuz Music 2.1 Contact Form
- CVE-2019-25737MEDIUMStored XSS in Live Chat Unlimited 2.8.3 – Admin Session Compromise
- CVE-2019-25739MEDIUMGigToDo 1.3 Stored XSS Vulnerability in Proposal Descriptions
- CVE-2019-25742MEDIUMStored XSS in Zoner Real Estate WordPress Theme 4.1.1 – Admin Account Compromise Risk
- CVE-2019-25743MEDIUMWordPress Soliloquy Lite 2.5.6 Stored XSS Vulnerability
- CVE-2019-25744MEDIUMWordPress Popup Builder 3.49 Stored XSS Vulnerability – Exploit Prevention & Patch Guide