CVE-2020-21653: Myucms v2.2.1 contains a server-side request forgery (SSRF) in the component \controller\index.php, which can

This week

CRITICAL 9.1REMOTEDOWNGRADE

CVE-2020-21653 is a critical-severity flaw (CVSS 9.1) affecting myucms. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Myucms v2.2.1 contains a server-side request forgery (SSRF) in the component \controller\index.php, which can be exploited via the sj() method.

Why this priority

Critical 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	9.1 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.2% (top 31%)
CISA exploited list	No
Weakness	CWE-918
Published	2021-10-06
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: myucms project

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

Am I affected?

Timeline

2021-10-06 22:15 UTCPublished CVE record published
2026-06-17 03:03 UTCUpdated Record last modified

myucms project myucms DOWNGRADE

Affected: 2.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.2

1. Check installed version

apt-cache policy myucms || rpm -q myucms || myucms --version

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

apt-cache madison myucms sudo apt install myucms=<VERSION_BEFORE_2.2> sudo apt-mark hold myucms

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

dnf --showduplicates list myucms sudo dnf downgrade myucms-<VERSION_BEFORE_2.2> sudo dnf versionlock add myucms

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-21653?

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

Is CVE-2020-21653 being exploited?

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

CVE-2020-21653 affects myucms. Severity is critical (CVSS 9.1). Myucms v2.2.1 contains a server-side request forgery (SSRF) in the component \controller\index.php, which can be exploited via the sj() method.

How urgent is CVE-2020-21653?

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

Software pages

PHP vulnerabilities

Related CVEs

CVE-2020-21652 CRITICAL 9.8 DOWNGRADE Myucms v2.2.1 contains a remote code execution (RCE) vulnerability in the component \controller\Config.php, wh
CVE-2020-21651 CRITICAL 9.8 DOWNGRADE Myucms v2.2.1 contains a remote code execution (RCE) vulnerability in the component \controller\point.php, whi
CVE-2020-21650 HIGH 8.8 DOWNGRADE Myucms v2.2.1 contains a remote code execution (RCE) vulnerability in the component \controller\Config.php, wh
CVE-2020-21649 HIGH 8.1 DOWNGRADE Myucms v2.2.1 contains a server-side request forgery (SSRF) in the component \controller\index.php, which can

References

← Back to latest CVEs