VulnerabilityPublished 3 Jun 2025

CVE-2025-43925: Inadequate Encryption Strength

Source CVE Database V5

Not known to be exploited · CVSS 4.6 Medium.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

4.6Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
n/a n/a	Affected =7.6.1	Fixed in–

AI-suggested

European organizations should prioritize the following mitigations: 1) Upgrade or patch Unicom Focal Point to a version where this vulnerability is addressed once the vendor releases a fix. 2) Until a patch is available, restrict access to the affected system to trusted users only and enforce strict privilege management to minimize the risk of exploitation. 3) Monitor and audit user activities and access logs for suspicious behavior that could indicate attempts to exploit this vulnerability. 4) Employ network segmentation and firewall rules to limit remote access to the application, reducing the attack surface. 5) If possible, encrypt sensitive data at rest using external encryption mechanisms or database-level encryption that does not rely on the application’s internal encryption. 6) Conduct security awareness training to reduce the risk of social engineering that could lead to privilege escalation or user interaction exploitation. 7) Prepare incident response plans specifically for data breaches involving this product to ensure rapid containment and remediation.

Description

An issue was discovered in Unicom Focal Point 7.6.1. The database is encrypted with a hardcoded key, making it easier to recover the cleartext data.

Impact

For European organizations using Unicom Focal Point 7.6.1, this vulnerability poses a risk to the confidentiality and integrity of sensitive data stored within the product's database. Since the encryption key is hardcoded, attackers with network access and some level of privileges could potentially decrypt sensitive information, leading to data breaches or unauthorized data manipulation. This could include intellectual property, customer data, or strategic project information managed within the tool. The requirement for user interaction and privileges somewhat limits the ease of exploitation, but insider threats or social engineering could facilitate this. The impact is particularly relevant for sectors with strict data protection regulations such as GDPR, where unauthorized data disclosure can lead to significant legal and financial penalties. Additionally, compromised data integrity could affect decision-making processes and project outcomes. Although availability is not impacted, the breach of confidentiality and integrity can undermine trust and operational security.

CWE-326Inadequate Encryption Strength (opens in a new tab)
Class weaknessOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required.
Architecture and Design
Use an encryption scheme that is currently considered to be strong by experts in the field.
OWASP Cheat Sheets
Cryptographic Storage (opens in a new tab)
Key Management (opens in a new tab)
Transport Layer Protection (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.3 (opens in a new tab)
V6.2.7 (opens in a new tab)
V6.2.4 (opens in a new tab)
Attack patterns
Encryption Brute Forcing (opens in a new tab)
Brute Force (opens in a new tab)
Protocol Analysis (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Jul 2025, 06:04 UTC

WeaknessesCWE-326

Technical details

References

Community reviews

Related threats