How severe is CVE-2020-36397?

CVE-2020-36397 has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2020-36397?

CVE-2020-36397 affects the following packages: lavalite/cms (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2020-36397?

The records we use list no patched version of lavalite/cms for CVE-2020-36397. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2020-36397 in my Packagist dependencies?

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

How do I mitigate CVE-2020-36397 if there is no patch (or I can't update yet)?

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.

Is CVE-2020-36397 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2020-36397, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2020-36397?

CVE-2020-36397 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 44th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2020-36397?

CVE-2020-36397 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2020-36397 published, and has it been updated?

CVE-2020-36397 was published on July 2, 2021 and was last updated on October 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

CVE-2020-36397 — cms

MEDIUM

CVE-2020-36397 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in lavalite/cms. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

LavaLite Stored Cross-site Scripting vulnerability

Also known asGHSA-3cfg-rxh6-h2rh

Published

Jul 2, 2021

Updated

Oct 20, 2026

Affected

1 pkg

Patched

See advisory

Exploits

1 known

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs44th percentile — riskier than 44% of all scored CVEsHighest risk

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

🐘lavalite/cms

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

A stored cross site scripting (XSS) vulnerability in the /admin/contact/contact component of LavaLite 5.8.0 allows authenticated attackers to execute arbitrary web scripts or HTML via a crafted payload entered into the "New" parameter.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`lavalite/cms`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

lavalitelavalite

1 version

5.8.0

Exploits & PoCs

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

A stored cross site scripting (XSS) vulnerability in the /admin/contact/…

github.comNVDJul 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for lavalite/cms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of lavalite/cms for CVE-2020-36397. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
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

O3 Security · Impact-Aware SCA

Is CVE-2020-36397 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.4/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

OpenSSF Scorecard

Package health score

cms

1.8/10

Maintained0/10

Code-Review0/10

Branch-ProtectionN/A

Assessed Nov 2, 2026

Timeline

Disclosed

Jul 2, 2021

First exploit

Jul 6, 2021

4 days after disclosure — rapid exploitation

Last updated

Oct 20, 2026

Identifiers

CVE-2020-36397

GHSA-3cfg-rxh6-h2rh

References

Advisorynvd.nist.gov · CVE 2020 36397 Reportgithub.com

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs affecting lavalite/cms are rated as high or higher (top: critical).

CVE-2025-71177CVE-2024-31828CVE-2023-30124CVE-2023-27238CVE-2023-27237CVE-2022-42188CVE-2020-28124CVE-2020-36396

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 20, 2026