CVE-2020-37073: Victor CMS 1.0 contains an authenticated file upload vulnerability that allows administrators to upload PHP fi

This month

HIGH 8.8DOWNGRADE

CVE-2020-37073 is a high-severity flaw (CVSS 8.8) 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 an authenticated file upload vulnerability that allows administrators to upload PHP files with arbitrary content through the user_image parameter. Attackers can upload a malicious PHP shell to the /img/ directory and execute system commands by accessing the uploaded file with a 'cmd' parameter.

Why this priority

High severity
Public exploit reference

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

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.5% (top 54%)
CISA exploited list	No
Weakness	CWE-434
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-37073?

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

Is CVE-2020-37073 being exploited?

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

CVE-2020-37073 affects victor cms. Severity is high (CVSS 8.8). Victor CMS 1.0 contains an authenticated file upload vulnerability that allows administrators to upload PHP files with arbitrary content through the user_image parameter. Attackers can upload a malicious PHP shell to the /img/ directory and

How urgent is CVE-2020-37073?

Priority 47/100. High severity; Public exploit reference

Software pages

PHP vulnerabilities

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-37072 HIGH 7.2 DOWNGRADE Victor CMS 1.0 contains a stored cross-site scripting vulnerability in the 'comment_author' POST parameter tha
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