LiveActive security incident?Get immediate response
CVE Record

CVE-2019-13970: In antSword before 2.1.0, self-XSS in the database configuration leads to code execution via modules/databa...

In antSword before 2.1.0, self-XSS in the database configuration leads to code execution via modules/database/asp/index.js, modules/database/custom/index.js, modules/database/index.js, or modules/database/php/index.js.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2019-13970 affects antSword versions before 2.1.0. A self-XSS flaw in database configuration could lead to code execution in the antSword client context. The available sources do not show broad exploitation, internet exposure, CVSS scoring, or detailed affected platform data.

Executive priority

Prioritize remediation where antSword is actively used by operators or administrators. This is not supported as a mass-exploitation emergency by the supplied sources, but code execution in a security tool warrants prompt cleanup.

Technical view

The CVE describes self-XSS in antSword database configuration paths, including database ASP, custom, generic, and PHP module index files. The vulnerability is stated to lead to code execution. Public references are GitHub issue, commit, and comparison links; no CWE, CVSS, or KEV evidence is provided.

Likely exposure

Exposure is likely limited to environments using antSword before 2.1.0, especially users interacting with database configuration functionality. The provided CVE data does not identify CPEs, hosted deployments, or third-party products embedding antSword.

Exploitation context

The source describes self-XSS, implying user interaction or control of configuration input is involved. There is no KEV listing and no cited evidence of active exploitation in the provided bundle.

Researcher notes

Evidence is sparse: the CVE record names antSword before 2.1.0 and database module paths, but omits CVSS, CWE, CPEs, exploit details, and operational indicators. Treat the GitHub issue and commit as primary technical references.

Mitigation direction

  • Move antSword installations off versions before 2.1.0.
  • Review the referenced AntSword issue and commit for vendor-specific fix context.
  • Restrict antSword use to trusted administrative workstations and users.
  • Audit database configuration entries for unexpected or unsafe content.

Validation and detection

  • Inventory antSword installations and confirm version 2.1.0 or later.
  • Check whether the referenced database module files exist in vulnerable versions.
  • Confirm the codebase includes the referenced fix commit or equivalent changes.
  • Review local antSword usage history for suspicious database configuration changes.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-13970 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.