dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-9144

HIGH · 7.6 CVSS v3.1 Published 2026-05-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
Taiko AG1000-01A SMS Alert Gateway Rev 7.3 and Rev 8 contains a stored cross-site scripting vulnerability in the embedded web configuration interface that allows authenticated attackers to execute persistent JavaScript by fragmenting malicious payloads across multiple administrative form fields. Attackers can bypass front-end length restrictions using JavaScript comments and template literals to concatenate executable script fragments that are rendered in administrative dashboard views such as index.zhtml, resulting in persistent script execution within administrative sessions.

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 · high confidence

Stored XSS vulnerability in Taiko AG1000-01A SMS Alert Gateway versions 7.3 and 8 allows authenticated attackers to inject persistent JavaScript into the web configuration interface. Attackers bypass client-side length restrictions by fragmenting malicious payloads across multiple administrative form fields using JavaScript comments and template literals, with payloads executing in admin dashboard views like index.zhtml.

MitigationImplement server-side input validation with strict length limits per field, apply context-aware output encoding for all rendered administrative dashboard views, and sanitize or reject special characters that enable payload fragmentation (comments, template literals).

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

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
Unchanged
Confidentiality
High
Integrity
High
Availability
Low

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

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 installed firmware/software version
    Access the product web interface (typically at the management URL) and navigate to the System Information, About, or Status page to find the firmware version. Alternatively, check via CLI if SSH/telnet access is available using commands like 'show version' or 'system info'.
    Affected if The version is Rev 7.3 or Rev 8, or falls within the affected range between these versions.
  2. Verify the web configuration interface is enabled
    Confirm that the web-based management interface (HTTP/HTTPS) is accessible and operational by attempting to reach the login page. Check the product documentation or running configuration for web interface enablement status.
    Affected if The web interface is enabled and accessible, making the XSS vulnerability reachable.
  3. Inspect stored configuration fields for suspicious content
    Log into the administrative dashboard and review form fields in the configuration sections (especially those allowing user-supplied text such as alert messages, device names, or notification templates). Look for unusual JavaScript fragments, template literals, or comment-wrapped content that may appear fragmented across multiple fields.
    Affected if Any stored JavaScript fragments, template literals, or fragmented code is found in configuration fields that were not intentionally configured by administrators.
  4. Check the index.zhtml dashboard page for unexpected script execution
    Navigate to the index.zhtml administrative dashboard page (or equivalent main dashboard) while monitoring browser developer tools for any injected script execution or reviewing page source for unauthorized script tags.
    Affected if Scripts execute or suspicious script tags appear when viewing the dashboard, indicating stored XSS is present.
  5. Review authentication logs for unauthorized access
    Examine authentication and access logs (via web interface log viewer, syslog, or local log files) for any unauthorized login attempts or sessions that may have been used to inject the XSS payload.
    Affected if Suspicious authentication activity correlates with timing of potential payload injection.

Your environment is affected if the Taiko AG1000-01A SMS Alert Gateway is running Rev 7.3 or Rev 8, has the web interface enabled, and contains any fragmented or concatenated JavaScript payloads stored in configuration fields that execute on dashboard pages.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement server-side input validation with strict length limits per field, apply context-aware output encoding for all rendered administrative dashboard views, and sanitize or reject special characters that enable payload fragmentation (comments, template literals).

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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