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

CVE-2026-43892

HIGH · 8.8 CVSS v3.1 Published 2026-05-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
AntSword is a cross-platform website management toolkit. Prior to 2.1.16, incomplete noxss() sanitization leads to 1-click RCE via jquery.terminal format code injection. This vulnerability is fixed in 2.1.16.

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

AntSword prior to version 2.1.16 contains incomplete sanitization in its noxss() function, which fails to properly neutralize jquery.terminal format code injection vectors. An attacker can achieve remote code execution through a single click by exploiting this format injection in the jquery.terminal library component.

MitigationUpgrade AntSword to version 2.1.16 or later to obtain the complete noxss() sanitization fix.

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 AntSword version
    Locate and read the version file or package manifest in your AntSword installation directory (commonly version.json, package.json, or the application's 'about' dialog). Compare the version number to 2.1.16.
    Affected if The installed version is lower than 2.1.16 (e.g., 2.1.15, 2.1.0, 2.0.x, etc.)
  2. Locate the noxss() function
    Search for the noxss function definition in AntSword source files, typically found in core filter or sanitization modules. Inspect the function code to verify if it includes sanitization logic for jquery.terminal format sequences.
    Affected if The noxss() function exists but lacks jquery.terminal format code handling (e.g., lacks handling of [[;color;]text] or similar terminal formatting patterns)
  3. Confirm jquery.terminal component presence
    Check if the jquery.terminal library is loaded or bundled in your AntSword installation. Look for jquery.terminal.js or similar files in the dependencies or public library directories.
    Affected if jquery.terminal library is present and loaded by the application
  4. Verify noxss() is invoked on user input
    Trace code paths where user-provided data passes through noxss() before rendering in terminal interfaces. Search for noxss() calls in request handlers or output rendering routines.
    Affected if User input flows through noxss() to jquery.terminal output without additional sanitization beyond noxss()

You are affected if your AntSword version is below 2.1.16, the jquery.terminal component is in use, and the noxss() function does not properly handle jquery.terminal format code injection.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade AntSword to version 2.1.16 or later to obtain the complete noxss() sanitization fix.

Recommended fix High confidence

AntSword version 2.1.16

  1. Check current AntSword version by examining the application or checking the installed files
  2. Backup all existing AntSword configurations, data, and shell scripts before upgrading
  3. Navigate to the official AntSword GitHub repository at github.com/antsword-project/antsword
  4. Download the version 2.1.16 release package from the releases section
  5. Extract the new version files, replacing the existing installation
  6. Verify the upgrade was successful by checking the application version
  7. Test that the application functions normally with existing shells and configurations

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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