CVE-2025-3920

CVE-2025-3920 is a high-severity vulnerability with a CVSS 4.0 base score of 8.5. 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 vulnerability was identified in SUR-FBD CMMS where hard-coded credentials were found within a compiled DLL file. These credentials correspond to a built-in administrative account of the software. An attacker with local access to the system or the application's installation directory could extract these credentials, potentially leading to a complete compromise of the application's administrative functions. This issue was fixed in version 2025.03.27 of the SUR-FBD CMMS software.

Frequently asked questions

What is CVE-2025-3920?
A vulnerability was identified in SUR-FBD CMMS where hard-coded credentials were found within a compiled DLL file. These credentials correspond to a built-in administrative account of the software. An attacker with local access to the system or the application's installation directory could extract these credentials, potentially leading to a complete compromise of the application's administrative functions. This issue was fixed in version 2025.03.27 of the SUR-FBD CMMS software.
How severe is CVE-2025-3920?
CVE-2025-3920 has a CVSS 4.0 base score of 8.5, rated high severity.
Is CVE-2025-3920 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (2nd percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2025-3920?
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-3920 have an EU (EUVD) identifier?
Yes. CVE-2025-3920 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-20198.
When was CVE-2025-3920 published?
CVE-2025-3920 was published on 2025-07-07 and last updated on 2026-06-17.

References

Other CWE-259 vulnerabilities

Browse all CWE-259 vulnerabilities →