NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

CVE-2019-13970 — antsword

MEDIUMFix: AntSwordProject/antSword@4b932e8

CVE-2019-13970 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in antsword. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for antsword — see the affected versions and patch details below.

AntSword RCE and XSS via code injection

Also known asGHSA-hq75-ggc3-8h3q
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs79th percentile — riskier than 79% of all scored CVEsHighest risk
0.00%0.79%1.58%2.37%0.5%1.9%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
antswordnpm
10downloads / week

Description

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.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmantswordall versions2.1.0npm install antsword@2.1.0

Affected Products

1 product · 1 configurations
Application
antswordantsword_project
< 2.1.0
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

In antSword before 2.1.0, self-XSS in the database configuration leads t…

github.comNVDJul 2019

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for antsword, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update antsword to 2.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-13970 is resolved across your whole dependency graph.

  3. Workarounds

    Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2019-13970 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2019-13970: antsword XSS — Fixed in 2.1.0