CVE-2020-23711: SQL Injection vulnerability in NavigateCMS 2.9 via the URL encoded GET input category in navigate.php.

This week

CRITICAL 9.8REMOTEDOWNGRADE

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

SQL Injection vulnerability in NavigateCMS 2.9 via the URL encoded GET input category in navigate.php.

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.5% (top 26%)
CISA exploited list	No
Weakness	CWE-89
Published	2021-06-28
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: naviwebs

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

Am I affected?

Timeline

2021-06-28 17:15 UTCPublished CVE record published
2026-06-17 03:04 UTCUpdated Record last modified

naviwebs navigate cms DOWNGRADE

Affected: 2.9

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.9

1. Check installed version

apt-cache policy navigate-cms || rpm -q navigate-cms || navigate-cms --version

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

apt-cache madison navigate-cms sudo apt install navigate-cms=<VERSION_BEFORE_2.9> sudo apt-mark hold navigate-cms

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

dnf --showduplicates list navigate-cms sudo dnf downgrade navigate-cms-<VERSION_BEFORE_2.9> sudo dnf versionlock add navigate-cms

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-23711?

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

Is CVE-2020-23711 being exploited?

CVE-2020-23711 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-23711 affect?

CVE-2020-23711 affects navigate cms. Severity is critical (CVSS 9.8). SQL Injection vulnerability in NavigateCMS 2.9 via the URL encoded GET input category in navigate.php.

How urgent is CVE-2020-23711?

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

Software pages

PHP vulnerabilities

Related CVEs

CVE-2022-28117 MEDIUM 4.9 DOWNGRADE A Server-Side Request Forgery (SSRF) in feed_parser class of Navigate CMS v2.9.4 allows remote attackers to fo
CVE-2021-44299 MEDIUM 5.4 DOWNGRADE A reflected cross-site scripting (XSS) vulnerability in \lib\packages\themes\themes.php of Navigate CMS v2.9.4
CVE-2021-36455 HIGH 8.8 DOWNGRADE SQL Injection vulnerability in Naviwebs Navigate CMS 2.9 via the quicksearch parameter in \lib\packages\commen
CVE-2021-36454 MEDIUM 5.4 DOWNGRADE Cross Site Scripting (XSS) vulnerability in Naviwebs Navigate Cms 2.9 via the navigate-quickse parameter to 1)

References

← Back to latest CVEs