CVE-2020-37072: Victor CMS 1.0 contains a stored cross-site scripting vulnerability in the 'comment_author' POST parameter tha

This week

HIGH 7.2REMOTEDOWNGRADE

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

Victor CMS 1.0 contains a stored cross-site scripting vulnerability in the 'comment_author' POST parameter that allows attackers to inject malicious scripts. Attackers can submit crafted JavaScript payloads through the comment submission form to execute arbitrary code in victim browsers.

Why this priority

High 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	7.2 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.3% (top 80%)
CISA exploited list	No
Weakness	CWE-79
Published	2026-02-03
Last modified	2026-06-17

Publisher (CNA): VulnCheck · Vendor: victor cms project

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

Am I affected?

Timeline

2026-02-03 22:16 UTCPublished CVE record published
2026-06-17 03:16 UTCUpdated Record last modified

victor cms project victor cms DOWNGRADE

Affected: 1.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.0

1. Check installed version

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

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

apt-cache madison victor-cms sudo apt install victor-cms=<VERSION_BEFORE_1.0> sudo apt-mark hold victor-cms

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

dnf --showduplicates list victor-cms sudo dnf downgrade victor-cms-<VERSION_BEFORE_1.0> sudo dnf versionlock add victor-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-37072?

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

Is CVE-2020-37072 being exploited?

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

CVE-2020-37072 affects victor cms. Severity is high (CVSS 7.2). Victor CMS 1.0 contains a stored cross-site scripting vulnerability in the 'comment_author' POST parameter that allows attackers to inject malicious scripts. Attackers can submit crafted JavaScript payloads through the comment submission fo

How urgent is CVE-2020-37072?

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

Related CVEs

CVE-2020-37076 HIGH 8.2 DOWNGRADE Victor CMS version 1.0 contains a SQL injection vulnerability in the 'post' parameter on post.php that allows
CVE-2020-37073 HIGH 8.8 DOWNGRADE Victor CMS 1.0 contains an authenticated file upload vulnerability that allows administrators to upload PHP fi
CVE-2020-36942 HIGH 8.8 DOWNGRADE Victor CMS 1.0 contains a file upload vulnerability that allows authenticated users to upload malicious PHP fi

References

← Back to latest CVEs