LiveActive security incident?Get immediate response
CVE Record

CVE-2025-0670: IDOR in Akinsoft's ProKuafor

Authorization Bypass Through User-Controlled Key vulnerability in Akinsoft ProKuafor allows Resource Leak Exposure. This issue affects ProKuafor: from s1.02.07 before v1.02.08.

MediumCVSS 4.7Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-0670 is an authorization flaw in Akinsoft ProKuafor. A highly privileged user may be able to manipulate a user-controlled key and access or affect resources they should not. The published severity is medium, with limited confidentiality, integrity, and availability impact.

Executive priority

Treat this as a targeted medium-priority update. Prioritize if ProKuafor stores sensitive customer, appointment, employee, or business data, or if many privileged users have access. It is less urgent than unauthenticated critical flaws but should not remain unresolved.

Technical view

The CVE describes CWE-639, Authorization Bypass Through User-Controlled Key, affecting Akinsoft ProKuafor from s1.02.07 before v1.02.08. CVSS 3.1 is 4.7: network-accessible, low complexity, high privileges required, no user interaction, unchanged scope, and low C/I/A impact.

Likely exposure

Exposure is limited to organizations running Akinsoft ProKuafor version s1.02.07 or other builds before v1.02.08. The CVE record lists default status as unaffected outside the specified affected version range.

Exploitation context

No active exploitation is indicated in the provided sources, and the CVE is not marked as CISA KEV. The vulnerability requires high privileges, reducing likelihood of broad unauthenticated exploitation, but it may matter in insider, compromised-account, or privilege-boundary scenarios.

Researcher notes

Available public detail is sparse. The core issue is IDOR-style authorization bypass via a user-controlled key. Avoid assuming exploitability beyond the CVSS conditions: network access and high privileges required. Validate affected versions and authorization boundaries in a controlled, non-destructive manner.

Mitigation direction

  • Identify any deployed Akinsoft ProKuafor instances and confirm their exact version.
  • Upgrade affected ProKuafor deployments to v1.02.08 or later, if available from Akinsoft.
  • Review Akinsoft or Turkish authority advisories for product-specific remediation guidance.
  • Restrict administrative access to ProKuafor until affected systems are updated.
  • Monitor for unusual access to records outside expected user responsibilities.

Validation and detection

  • Confirm ProKuafor version is not s1.02.07 or below v1.02.08.
  • Verify role-based access controls prevent cross-user or cross-tenant resource access.
  • Review application logs for unauthorized resource access patterns.
  • Document compensating controls if upgrade timing depends on vendor guidance.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-639: 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 lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-0670 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.7 (3.1)
Known Exploited
No
Published

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

Official CVE source material

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.

1CVSS vectors
3Timeline events
1ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
4.7CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L1.23.4TR-CERT

Vulnerability scoring details

Base CVSS 3.1 score

4.7Medium
CVSS 3.1 vector shape for CVE-2025-0670Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AkinsoftProKuafors1.02.07unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-639 · source CWE mapping

Authorization Bypass Through User-Controlled Key

Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.