CVE-2020-10057: GeniXCMS 1.1.7 is vulnerable to user privilege escalation due to broken access control

This month

HIGH 8.8DOWNGRADE

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

GeniXCMS 1.1.7 is vulnerable to user privilege escalation due to broken access control. This issue exists because of an incomplete fix for CVE-2015-2680, in which "token" is used as a CSRF protection mechanism, but without validation that "token" is associated with an administrative user.

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	None
User interaction	Required
EPSS exploit chance	0.9% (top 40%)
CISA exploited list	No
Weakness	CWE-352
Published	2020-03-04
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: metalgenix

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

Am I affected?

Timeline

2020-03-04 19:15 UTCPublished CVE record published
2026-06-17 02:47 UTCUpdated Record last modified

metalgenix genixcms DOWNGRADE

Affected: 1.1.7

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.1.7

1. Check installed version

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

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

apt-cache madison genixcms sudo apt install genixcms=<VERSION_BEFORE_1.1.7> sudo apt-mark hold genixcms

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

dnf --showduplicates list genixcms sudo dnf downgrade genixcms-<VERSION_BEFORE_1.1.7> sudo dnf versionlock add genixcms

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

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

Is CVE-2020-10057 being exploited?

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

CVE-2020-10057 affects genixcms. Severity is high (CVSS 8.8). GeniXCMS 1.1.7 is vulnerable to user privilege escalation due to broken access control. This issue exists because of an incomplete fix for CVE-2015-2680, in which "token" is used as a CSRF protection mechanism, but without validation that "

How urgent is CVE-2020-10057?

Priority 51/100. High severity; Public exploit reference

Related CVEs

CVE-2022-24563 MEDIUM 5.4 DOWNGRADE In Genixcms v1.1.11, a stored Cross-Site Scripting (XSS) vulnerability exists in /gxadmin/index.php?page=theme
CVE-2018-14476 MEDIUM 6.1 DOWNGRADE GeniXCMS 1.1.5 has XSS via the dbuser or dbhost parameter during step 1 of installation.
CVE-2017-8827 CRITICAL 9.1 DOWNGRADE forgotpassword.php in GeniXCMS 1.0.2 lacks a rate limit, which might allow remote attackers to cause a denial
CVE-2017-8780 MEDIUM 4.8 DOWNGRADE GeniXCMS 1.0.2 has XSS triggered by a comment that is mishandled during a publish operation by an administrato
CVE-2017-8762 MEDIUM 5.4 DOWNGRADE GeniXCMS 1.0.2 has XSS triggered by an authenticated user who submits a page, as demonstrated by a crafted onc

References

← Back to latest CVEs