How severe is CVE-2020-28672?

CVE-2020-28672 has a CVSS 3.x base score of 7.2, rated high severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2020-28672 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 12% (96th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2020-28672?

CVE-2020-28672 affects Monocms. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2020-28672?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2020-28672 published?

CVE-2020-28672 was published on 2021-01-07 and last updated on 2026-06-17.

CVE-2020-28672

CVE-2020-28672 is a high-severity vulnerability in Monocms with a CVSS 3.x base score of 7.2. Its EPSS exploit-prediction score of 12% places it in the 96th percentile, indicating an elevated likelihood of exploitation.

Key facts

Severity: High (CVSS 3.x base score 7.2)
CVSS v2: 9.0
EPSS exploit prediction: 12% (96th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Monocms
Published: 2021-01-07
Last modified: 2026-06-17

Description

MonoCMS Blog 1.0 is affected by incorrect access control that can lead to remote arbitrary code execution. At monofiles/category.php:27, user input can be saved to category/[foldername]/index.php causing RCE.

Frequently asked questions

What is CVE-2020-28672?: MonoCMS Blog 1.0 is affected by incorrect access control that can lead to remote arbitrary code execution. At monofiles/category.php:27, user input can be saved to category/[foldername]/index.php causing RCE.
How severe is CVE-2020-28672?: CVE-2020-28672 has a CVSS 3.x base score of 7.2, rated high severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2020-28672 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 12% (96th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-28672?: CVE-2020-28672 affects Monocms. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2020-28672?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2020-28672 published?: CVE-2020-28672 was published on 2021-01-07 and last updated on 2026-06-17.

References

https://github.com/fortest-1/vuln/blob/main/MonoCMS%20Blog/MonoCMS%20Blog%201.0_remote_code_execution.md

Affected products (1)

cpe:2.3:a:monocms:monocms:1.0:*:*:*:*:*:*:*

More vulnerabilities in Monocms

CVE-2020-25985 — High (CVSS 8.1): MonoCMS Blog 1.0 is affected by: Arbitrary File Deletion. Any authenticated user can delete files on and off the…
CVE-2020-25987 — High (CVSS 7.5): MonoCMS Blog 1.0 stores hard-coded admin hashes in the log.xml file in the source files for MonoCMS Blog. Hash type is…
CVE-2020-25986 — Medium (CVSS 6.5): A Cross Site Request Forgery (CSRF) vulnerability in MonoCMS Blog 1.0 allows attackers to change the password of a user.
CVE-2024-10928 — Low (CVSS 3.5): A vulnerability was found in MonoCMS up to 20240528. It has been declared as problematic. Affected by this…
CVE-2024-10927 — Low (CVSS 3.5): A vulnerability was found in MonoCMS up to 20240528. It has been classified as problematic. Affected is an unknown…

All CVEs affecting Monocms →