CVE-2020-18013: SQL Injextion vulnerability exists in Whatsns 4.0 via the ip parameter in index.php?admin_banned/add.htm.

This week

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2020-18013 is a critical-severity flaw (CVSS 9.8) affecting whatsns. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

SQL Injextion vulnerability exists in Whatsns 4.0 via the ip parameter in index.php?admin_banned/add.htm.

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.4% (top 28%)
CISA exploited list	No
Weakness	CWE-89
Published	2021-07-30
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: whatsns

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2021-07-30 14:15 UTCPublished CVE record published
2026-06-17 02:59 UTCUpdated Record last modified

whatsns whatsns DOWNGRADE

Affected: 4.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 4.0

1. Check installed version

apt-cache policy whatsns || rpm -q whatsns || whatsns --version

2. No fixed release: DOWNGRADE to a release before 4.0 (Debian / Ubuntu)

apt-cache madison whatsns sudo apt install whatsns=<VERSION_BEFORE_4.0> sudo apt-mark hold whatsns

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list whatsns sudo dnf downgrade whatsns-<VERSION_BEFORE_4.0> sudo dnf versionlock add whatsns

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-18013?

whatsns: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2020-18013 being exploited?

CVE-2020-18013 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-18013 affect?

CVE-2020-18013 affects whatsns. Severity is critical (CVSS 9.8). SQL Injextion vulnerability exists in Whatsns 4.0 via the ip parameter in index.php?admin_banned/add.htm.

How urgent is CVE-2020-18013?

Priority 62/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

PHP vulnerabilities

Related CVEs

CVE-2019-11452 HIGH 7.2 DOWNGRADE whatsns 4.0 allows index.php?admin_category/remove.html cid[] SQL injection.
CVE-2019-11451 HIGH 7.2 DOWNGRADE whatsns 4.0 allows index.php?inform/add.html qid SQL injection.
CVE-2019-11450 CRITICAL 9.8 DOWNGRADE whatsns 4.0 allows index.php?question/ajaxadd.html title SQL injection.

References

← Back to latest CVEs