MEDIUM 5.4

CVE-2026-12621: GridTime 3000 Password Reset XSS Vulnerability

A cross-site scripting (XSS) vulnerability exists in the password reset form of GridTime 3000. An attacker with valid login credentials can inject malicious JavaScript code that executes in the browser of other users viewing the form, potentially stealing session cookies, credentials, or triggering unauthorized actions. The vulnerability affects versions 1.0r0.03 through 1.1.x, with the fix available in version 1.2r0.0 and later.

Source data · NVD / CISA · public domain

CVSS
3.1 · 5.4 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Weaknesses (CWE)
CWE-79
Affected products
2 configuration(s)
Published / Modified
2026-06-19 / 2026-07-09

NVD description (verbatim)

Improper neutralization of input during web page generation XSS vulnerability in the GridTime 3000 (password reset form) allows XSS. This issue affects GridTime 3000: from 1.0r0.03 before 1.2r0.0.

1 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-12621 is a reflected or stored XSS flaw (CWE-79) in the GridTime 3000 password reset form that fails to properly sanitize user-supplied input before rendering it in the HTML response. The vulnerability requires authentication (PR:L) and user interaction (UI:R)—specifically, a victim must visit a malicious link or the attacker must store the payload within the application. The scope is changed (S:C), meaning the XSS impact extends beyond the vulnerable component to affect other users' sessions and the broader application context. This results in confidentiality and integrity impacts with a CVSS 3.1 score of 5.4 (MEDIUM).

Business impact

An authenticated attacker can compromise the accounts and sessions of administrators or other authorized users through social engineering, phishing, or stored payload attacks. This threatens password reset workflows—a critical authentication mechanism—creating risk of account takeover, unauthorized access, and potential lateral movement to administrative functions. The authentication requirement limits immediate blast radius but does not eliminate risk, as compromised low-privilege accounts or accounts obtained through credential stuffing remain viable attack vectors.

Affected systems

GridTime 3000 (both the firmware and product itself) versions 1.0r0.03 through versions prior to 1.2r0.0 are vulnerable. Manufactured by Microchip, GridTime 3000 is commonly deployed in industrial and embedded applications. Organizations running any GridTime 3000 instance should verify their installed version immediately.

Exploitability

Exploitation requires valid credentials to access the password reset form, limiting the attack surface to authenticated users or those with compromised accounts. No public exploit code or active in-the-wild exploitation is currently documented (KEV status: not listed). However, the attack is straightforward once a foothold exists—injection payloads are easily crafted, and user interaction (clicking a link or viewing stored content) is achievable through social engineering. The network-accessible attack vector (AV:N) and low complexity (AC:L) mean that once authenticated, delivery is trivial.

Remediation

Upgrade GridTime 3000 to version 1.2r0.0 or later. Microchip has patched the input validation and output encoding in the password reset form. Organizations unable to patch immediately should restrict access to the password reset function via network-level controls, monitor authentication logs for suspicious session activity, and consider temporary disabling of password reset via self-service until patching completes.

Patch guidance

Verify your GridTime 3000 version by checking the device's firmware version string or management interface. Versions 1.0r0.03 through 1.1.x require upgrade. Microchip has released version 1.2r0.0 as the fixed build—consult the vendor's security advisory for detailed upgrade procedures, including any firmware staging or rollback contingencies specific to your deployment. Test patches in a non-production environment first, as GridTime 3000 may be integrated with critical operational systems.

Detection guidance

Monitor HTTP traffic to GridTime 3000's password reset endpoint (/password-reset or similar) for unusual query parameters, POST data, or header values containing script tags, event handlers, or HTML entities. Enable application logging for the password reset form and review logs for inputs containing 'javascript:', 'onerror=', 'onclick=', or other DOM event attributes. Search for stored payloads in user records or session data. Implement Web Application Firewall (WAF) rules to block common XSS patterns before they reach the application.

Why prioritize this

Although CVSS 5.4 rates this as MEDIUM severity, the attack surface is constrained by the authentication requirement (PR:L) and user interaction (UI:R), which justify the lower score. However, the password reset form is a sensitive authentication mechanism, and successful exploitation enables account takeover. Organizations should prioritize patching within 60–90 days, earlier if GridTime 3000 is internet-facing or serves high-value administrative accounts. The lack of KEV listing suggests low current exploitation pressure, which may allow a measured patching window.

Risk score, explained

CVSS 3.1 score of 5.4 reflects: Network-accessible attack (AV:N), low complexity (AC:L), but requiring login (PR:L) and user interaction (UI:R). Scope is changed (S:C), indicating the vulnerability affects users beyond the directly targeted component. Confidentiality and Integrity impacts are low (C:L, I:L) because XSS typically allows session hijacking or data exfiltration rather than wholesale compromise. Availability is not affected (A:N). The MEDIUM rating appropriately reflects that while exploitation is achievable, it requires pre-existing access and social engineering, not a trivial remote unauthenticated attack.

Frequently asked questions

Do we need to patch if our GridTime 3000 is only accessible on a private internal network?

Yes. Insider threat, compromised employee accounts, and lateral movement from other breached systems all provide pathways for an authenticated attacker to reach GridTime 3000 even on internal networks. Additionally, network segmentation can fail or change. Treat this as a routine patching priority rather than deferring indefinitely based on network location alone.

Can an unauthenticated attacker exploit this vulnerability?

No. The vulnerability requires the attacker to either have valid credentials or trick an authenticated user into clicking a malicious link. This is why the CVSS score is MEDIUM rather than HIGH or CRITICAL. However, if your GridTime 3000 credentials are shared, default, or exposed in prior breaches, the practical barrier is lower than the technical requirement suggests.

What does 'scope changed' mean in the CVSS vector?

It means the XSS vulnerability can impact resources or users outside the password reset form itself—for example, by stealing administrator session tokens that grant access to other parts of the GridTime 3000 application. This is why the vulnerability receives a higher rating than a purely isolated XSS in a low-privilege user profile page would.

Is there a workaround if we cannot patch immediately?

Partial mitigations include: disabling the password reset form if an alternative account recovery process exists, restricting network access to the GridTime 3000 management interface to specific IP ranges, enforcing strong password policies and multi-factor authentication to reduce the value of session theft, and monitoring logs closely for signs of XSS exploitation. These are temporary measures and not substitutes for patching.

This analysis is provided for informational purposes and represents SEC.co's interpretation of CVE-2026-12621 as of the publication date. Exploit details, patch availability, and vendor guidance are subject to change. Organizations should verify patch version numbers, compatibility, and upgrade procedures against official Microchip security advisories and release notes before deploying fixes. SEC.co makes no guarantee of the accuracy, completeness, or timeliness of remediation steps and assumes no liability for damages resulting from the use or misuse of this information. Always consult your vendor's official security bulletins and conduct testing in a non-production environment before patching production systems. Source: NVD (public-domain), retrieved 2026-07-27. Analysis generated by SEC.co (claude-haiku-4-5).