CVE-2025-60375

CVE-2025-60375 is a high-severity vulnerability with a CVSS 3.x base score of 7.3. 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-289.

Key facts

Description

The authentication mechanism in Perfex CRM before 3.3.1 allows attackers to bypass login credentials due to insufficient server-side validation. By sending empty username and password parameters in the login request, an attacker can gain unauthorized access to user accounts, including administrative accounts, without providing valid credentials.

Frequently asked questions

What is CVE-2025-60375?
The authentication mechanism in Perfex CRM before 3.3.1 allows attackers to bypass login credentials due to insufficient server-side validation. By sending empty username and password parameters in the login request, an attacker can gain unauthorized access to user accounts, including administrative accounts, without providing valid credentials.
How severe is CVE-2025-60375?
CVE-2025-60375 has a CVSS 3.x base score of 7.3, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability low.
Is CVE-2025-60375 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (18th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2025-60375?
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.
Does CVE-2025-60375 have an EU (EUVD) identifier?
Yes. CVE-2025-60375 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-33558.
When was CVE-2025-60375 published?
CVE-2025-60375 was published on 2025-10-09 and last updated on 2026-06-17.

References

Other CWE-289 vulnerabilities

Browse all CWE-289 vulnerabilities →