dbcve.org
Gridtime 3000 FirmwareOperating system · Microchip

CVE-2026-12619

MEDIUM · 5.4 CVSS v3.1 Published 2026-06-19
Fix available
A fix is available. Upgrade to 1.2r0.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Microchip GridTime 3000 allows Cross-Site Scripting (XSS). This issue affects GridTime 3000: from 1.0r0.03 through 1.1r0.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Cross-Site Scripting (XSS) vulnerability in the web interface of Microchip GridTime 3000 timing device. The vulnerability stems from improper neutralization of user input during web page generation, allowing attackers to inject malicious scripts that execute in the browsers of users accessing the affected web interface.

MitigationImplement proper input validation and output encoding on all user-supplied data before rendering in web pages, or obtain and apply vendor-provided firmware update that addresses this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Gridtime 3000 FirmwareOperating system
Affected:>= 1.0r0.03, < 1.2r0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm device is a Microchip GridTime 3000
    Access the device web interface or check the device identification through its management interface. Look for product name/model information displaying 'GridTime 3000' or 'Gridtime 3000'.
    Affected if The device model is not GridTime 3000 - this vulnerability only affects that specific product.
  2. Check installed firmware version
    Log into the device web interface and navigate to the firmware version or system information page. Alternatively, access the device CLI or management console and retrieve the firmware version information.
    Affected if The firmware version is 1.0r0.03 or higher but lower than 1.2r0.0. Versions below 1.0r0.03 and version 1.2r0.0 or higher are not affected.
  3. Verify web interface is accessible
    Attempt to access the device web interface by navigating to the device IP address in a web browser. Confirm the login page or device status page loads successfully.
    Affected if The web interface is enabled and reachable on the network. If the web interface is disabled or blocked by network controls, the XSS vulnerability cannot be exploited through this vector.

You are affected if you have a Microchip GridTime 3000 device with firmware version 1.0r0.03 through 1.1rX and the web interface is currently accessible on your network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.2r0.0 or later
Fixed in 1.2r0.0
Interim mitigation

Implement proper input validation and output encoding on all user-supplied data before rendering in web pages, or obtain and apply vendor-provided firmware update that addresses this vulnerability.

Recommended fix High confidence

Firmware version 1.2r0.0 or later

  1. Verify current firmware version on the GridTime 3000 device through the web interface or CLI
  2. Download firmware version 1.2r0.0 or later from the official Microchip support portal at www.microchip.com
  3. Review Microchip firmware upgrade documentation for GridTime 3000
  4. Backup current device configuration if supported by the firmware backup feature
  5. Upload the firmware file through the device's firmware update interface
  6. Verify the upgrade was successful by checking the new firmware version
  7. Confirm all device functions are operating normally after the upgrade
Caveat Firmware upgrades on industrial devices may introduce compatibility changes; review release notes for any configuration or feature changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gridtime 3000 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-12619 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-12619 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data