CVE-2025-1100

CVE-2025-1100 is a critical-severity vulnerability in Q-free Maxtime with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-259.

Key facts

Description

A CWE-259 "Use of Hard-coded Password" for the root account in Q-Free MaxTime less than or equal to version 2.11.0 allows an unauthenticated remote attacker to execute arbitrary code with root privileges via SSH.

Frequently asked questions

What is CVE-2025-1100?
A CWE-259 "Use of Hard-coded Password" for the root account in Q-Free MaxTime less than or equal to version 2.11.0 allows an unauthenticated remote attacker to execute arbitrary code with root privileges via SSH.
How severe is CVE-2025-1100?
CVE-2025-1100 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2025-1100 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (50th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-1100?
CVE-2025-1100 affects Q-free Maxtime. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-1100?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
Does CVE-2025-1100 have an EU (EUVD) identifier?
Yes. CVE-2025-1100 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-2002.
When was CVE-2025-1100 published?
CVE-2025-1100 was published on 2025-02-12 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Q-free Maxtime

All CVEs affecting Q-free Maxtime →

Other CWE-259 vulnerabilities

Browse all CWE-259 vulnerabilities →