CVE-2018-10429: Cosmo 1.0.0Beta6 allows attackers to execute arbitrary PHP code via the Database Prefix field on the Database

This week

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2018-10429 is a critical-severity flaw (CVSS 9.8) affecting cosmo. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Cosmo 1.0.0Beta6 allows attackers to execute arbitrary PHP code via the Database Prefix field on the Database Info screen of install.php.

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.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.8% (top 22%)
CISA exploited list	No
Weakness	CWE-94
Published	2018-04-26
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: cosmocms

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

Am I affected?

Timeline

2018-04-26 17:29 UTCPublished CVE record published
2026-06-17 01:33 UTCUpdated Record last modified

cosmocms cosmo DOWNGRADE

Affected: 1.0.0 beta6

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.0.0

1. Check installed version

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

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

apt-cache madison cosmo sudo apt install cosmo=<VERSION_BEFORE_1.0.0> sudo apt-mark hold cosmo

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

dnf --showduplicates list cosmo sudo dnf downgrade cosmo-<VERSION_BEFORE_1.0.0> sudo dnf versionlock add cosmo

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-2018-10429?

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

Is CVE-2018-10429 being exploited?

CVE-2018-10429 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-2018-10429 affect?

CVE-2018-10429 affects cosmo. Severity is critical (CVSS 9.8). Cosmo 1.0.0Beta6 allows attackers to execute arbitrary PHP code via the Database Prefix field on the Database Info screen of install.php.

How urgent is CVE-2018-10429?

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

Software pages

PHP vulnerabilities

References

← Back to latest CVEs