CVE-2020-14927: Navigate CMS 2.9 allows XSS via the Alias or Real URL field of the "Web Sites > Create > Aliases > Add" screen

Routine

MEDIUM 4.8DOWNGRADE

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

Navigate CMS 2.9 allows XSS via the Alias or Real URL field of the "Web Sites > Create > Aliases > Add" screen.

Why this priority

Public exploit reference

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

Risk facts

CVSS score	4.8 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	Required
EPSS exploit chance	0.5% (top 54%)
CISA exploited list	No
Weakness	CWE-79
Published	2020-06-19
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

2020-06-19 17:15 UTCPublished CVE record published
2026-06-17 02:55 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-14927?

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

Is CVE-2020-14927 being exploited?

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

CVE-2020-14927 affects navigate cms. Severity is medium (CVSS 4.8). Navigate CMS 2.9 allows XSS via the Alias or Real URL field of the "Web Sites > Create > Aliases > Add" screen.

How urgent is CVE-2020-14927?

Priority 33/100. Public exploit reference

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)
CVE-2020-23711 CRITICAL 9.8 DOWNGRADE SQL Injection vulnerability in NavigateCMS 2.9 via the URL encoded GET input category in navigate.php.

References

← Back to latest CVEs