Security readout for executives and security teams
Plain-English summary
Perfektive versions before Version 12574 Build 2701 have an authentication weakness that may let an unauthenticated attacker bypass login controls or brute-force access. The issue is high severity because it is network-accessible, low complexity, and requires no user interaction.
Executive priority
Prioritize within the next patch cycle, faster for internet-facing or high-value Perfektive deployments. The business risk is unauthorized access through weak authentication controls, but exploitation evidence is not confirmed in the provided sources.
Technical view
The CVE cites CWE-307, CWE-602, and CWE-807: excessive authentication attempts are not properly restricted, security is enforced client-side, and untrusted input affects security decisions. CVSS 3.1 is 7.3 with low confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to organizations running Turkguven Perfektive before Version 12574 Build 2701. The bundle does not identify deployment models, internet exposure, affected modules, or CPEs.
Exploitation context
The source bundle does not show CISA KEV listing or public exploitation evidence. Treat exploitation status as unconfirmed, while prioritizing review because the vector is unauthenticated and network reachable.
Researcher notes
Evidence is sparse. The CVE record gives weakness classes, CVSS, and affected version boundary, but no exploit details, workaround, CPE, or module-level scope. Validate against vendor or government advisory before making final exposure calls.
Mitigation direction
- Inventory any Turkguven Perfektive deployments and record exact version and build.
- Upgrade to Version 12574 Build 2701 or later if vendor guidance confirms availability.
- Review the Turkish government advisory for current remediation details.
- Restrict access to Perfektive authentication surfaces until remediation is complete.
- Monitor authentication logs for repeated failures or unusual bypass indicators.
Validation and detection
- Confirm installed Perfektive versions are not before Version 12574 Build 2701.
- Verify authentication controls are enforced server-side after remediation.
- Check logs for abnormal authentication attempts around exposed Perfektive services.
- Confirm no unauthorized accounts, sessions, or configuration changes occurred.
- Document whether any instance is internet-facing or externally reachable.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-307: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-602: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-807: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-10161 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L3.93.4TR-CERTVulnerability scoring details
Base CVSS 3.1 score
7.3HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.usom.gov.tr/bildirim/tr-25-0387CVE reference, TR-CERT · government-resource, broken-link
- https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-25-0387CVE reference, TR-CERT · government-resource
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Restriction of Excessive Authentication Attempts
Improper Restriction of Excessive Authentication Attempts represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Client-Side Enforcement of Server-Side Security
Client-Side Enforcement of Server-Side Security represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Reliance on Untrusted Inputs in a Security Decision
Reliance on Untrusted Inputs in a Security Decision represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.