CVE-2025-51818: MCCMS 2.7.0 is vulnerable to Arbitrary file deletion in the Backups.php component

Routine

MEDIUM 5.4DOWNGRADE

CVE-2025-51818 is a medium-severity flaw (CVSS 5.4) affecting mccms. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

MCCMS 2.7.0 is vulnerable to Arbitrary file deletion in the Backups.php component. This allows an attacker to execute arbitrary commands

Why this priority

Public exploit reference

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

Risk facts

CVSS score	5.4 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 83%)
CISA exploited list	No
Weakness	CWE-552
Published	2025-08-21
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: chshcms

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

Am I affected?

Timeline

2025-08-21 14:15 UTCPublished CVE record published
2026-06-17 09:35 UTCUpdated Record last modified

chshcms mccms DOWNGRADE

Affected: 2.7

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.7

1. Check installed version

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

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

apt-cache madison mccms sudo apt install mccms=<VERSION_BEFORE_2.7> sudo apt-mark hold mccms

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

dnf --showduplicates list mccms sudo dnf downgrade mccms-<VERSION_BEFORE_2.7> sudo dnf versionlock add mccms

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-2025-51818?

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

Is CVE-2025-51818 being exploited?

CVE-2025-51818 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-2025-51818 affect?

CVE-2025-51818 affects mccms. Severity is medium (CVSS 5.4). MCCMS 2.7.0 is vulnerable to Arbitrary file deletion in the Backups.php component. This allows an attacker to execute arbitrary commands

How urgent is CVE-2025-51818?

Priority 28/100. Public exploit reference

Software pages

PHP vulnerabilities

Related CVEs

CVE-2025-50234 MEDIUM 6.5 DOWNGRADE MCCMS v2.7.0 has an SSRF vulnerability located in the index() method of the sys\apps\controllers\api\Gf.php fi
CVE-2025-5328 MEDIUM 5.4 DOWNGRADE A vulnerability was found in chshcms mccms 2.7
CVE-2025-5327 MEDIUM 6.3 DOWNGRADE A vulnerability was found in chshcms mccms 2.7
CVE-2025-51651 MEDIUM 5.5 DOWNGRADE An authenticated arbitrary file download vulnerability in the component /admin/Backups.php of Mccms v2.7.0 all

References

← Back to latest CVEs