dbcve.org
Gridtime 3000 FirmwareOperating system · Microchip

CVE-2026-12622

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
The GridTime 3000 GNSS Time Server has an open redirect vulnerability in the password change form submission. 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

The GridTime 3000 GNSS Time Server contains an open redirect vulnerability in the password change form submission. The application fails to properly validate the redirect URL parameter, allowing an attacker to craft a malicious link that redirects users to an arbitrary external website after completing a password change.

MitigationImplement strict server-side validation and whitelist-based filtering for any redirect URLs in the password change functionality to ensure only trusted destinations are allowed.

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. Identify the device product
    Confirm the target system is a Microchip GridTime 3000 GNSS Time Server by accessing the web interface login page, checking the device label, or running CLI commands such as 'show system info' or 'version' to verify the product name and model
    Affected if The device is not a GridTime 3000 GNSS Time Server by Microchip, then this CVE does not apply
  2. Check the installed firmware version
    Access the web interface (typically via HTTPS) and navigate to the Status, About, or System Information page to view the firmware version, or use the CLI command 'show version' or 'system info' to retrieve the firmware version number
    Affected if The firmware version is >= 1.0r0.03 AND < 1.2r0.0 - only versions in this range are affected by this vulnerability
  3. Verify password change functionality exists
    Log into the web interface and locate the password change or user settings section, typically found under Administration, User Management, or Account Settings menus to confirm the password change form is present and accessible
    Affected if The password change form is not present or not accessible, then the attack surface for this vulnerability does not exist
  4. Inspect redirect URL handling in password change flow
    Submit a password change request with a 'redirect', 'next', or 'url' parameter set to an external domain (such as example.com) in the HTTP request, then observe if the application redirects to the specified external URL after the password change is processed
    Affected if The application accepts and honors a redirect parameter pointing to an external domain, confirming the open redirect vulnerability is present

You are affected only if the device is a Microchip GridTime 3000 with firmware version >= 1.0r0.03 and < 1.2r0.0, AND the password change form processes an unchecked redirect URL parameter to external sites.

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 strict server-side validation and whitelist-based filtering for any redirect URLs in the password change functionality to ensure only trusted destinations are allowed.

Recommended fix Moderate confidence

1.2r0.0 or later

  1. Obtain GridTime 3000 firmware version 1.2r0.0 or later from Microchip's official support website
  2. Review Microchip's firmware update documentation for the GridTime 3000 device
  3. Upload and apply the firmware update following the manufacturer's standard upgrade procedure
  4. After updating, verify that the password change form no longer exhibits open redirect behavior by testing with a known redirect parameter
Caveat firmware updates on embedded timing devices may require downtime and should be tested in a staging environment first

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

Fix this in Gridtime 3000 Firmware Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-12622 — 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-12622 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