CVE-2026-22912
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 · uneditedImproper validation of a login parameter may allow attackers to redirect users to malicious websites after authentication. This can lead to various risk including stealing credentials from unsuspecting users.
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 confidenceThis is an open redirect vulnerability in a login parameter where the application redirects users to a URL after authentication without properly validating that the target URL is safe and legitimate. Attackers can craft malicious URLs containing arbitrary redirect targets, tricking authenticated users into visiting phishing or malicious sites that mimic the legitimate application to harvest credentials.
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< 1.5.0CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelCheck the device label, web interface header, or system information page for the exact model name 'Tdc X401gl' from SickAffected if The device is NOT a Sick Tdc X401gl model - this CVE does not apply
-
Check the installed firmware versionAccess the device web interface, navigate to System > Firmware/Version info, or use the command line interface with 'show version' or similar commandAffected if Firmware version is 1.5.0 or higher - the vulnerability is patched; versions below 1.5.0 are affected
-
Verify the login redirect parameter existsExamine the login form HTML source or intercept the authentication request to identify if a 'redirect', 'next', 'url', or similar parameter is passed after authenticationAffected if No redirect parameter is found in the login flow - the vulnerability may not be present even on vulnerable versions
-
Test for unvalidated redirectAfter successful authentication, append a test parameter such as '?redirect=http://example.com' or '?next=http://evil.com' to the login URL and verify if the application redirects to the external domain without validationAffected if The application redirects to an arbitrary external URL provided in the parameter - the vulnerability is confirmed present and exploitable
You are affected if you have a Sick Tdc X401gl device running firmware version below 1.5.0 and the login flow accepts and follows unvalidated redirect URLs.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.5.0
Implement strict allowlist-based validation for redirect URLs to ensure they point only to trusted, internal domains or paths, and reject any external or untrusted URLs.
1.5.0
- Identify the current firmware version of the Tdc X401gl device
- Access the device management interface or use the appropriate firmware update mechanism
- Upgrade the firmware to version 1.5.0 or later to address the open redirect vulnerability
- Verify the upgrade was successful and the device is functioning normally
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22912 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-22912 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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