LiveActive security incident?Get immediate response
CVE Record

CVE-2022-2177: SQL Injection in Kayrasoft

Kayrasoft product before version 2 has an unauthenticated SQL Injection vulnerability. This is fixed in version 2.

CriticalCVSS 9.4Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Kayrasoft versions before 2 contain a critical unauthenticated SQL injection flaw. An attacker could potentially access or change database data remotely without logging in. The public record says version 2 fixes it. Treat any pre-version-2 internet-facing deployment as urgent until verified upgraded.

Executive priority

High priority. Confirm whether Kayrasoft is used and upgrade any pre-version-2 deployment promptly, starting with externally reachable systems. The main business concern is unauthorized database access or alteration.

Technical view

CVE-2022-2177 is CWE-89 SQL injection in Kayrasoft before version 2. CVSS 3.1 is 9.4: network exploitable, low complexity, no privileges, no user interaction, with high confidentiality and integrity impact and low availability impact. Affected version details beyond “before version 2” are not provided.

Likely exposure

Exposure is likely where Kayrasoft before version 2 is deployed, especially if reachable over a network or the internet. The sources do not provide CPEs, specific modules, endpoints, or deployment indicators.

Exploitation context

The provided sources do not state active exploitation, and the CVE is not marked KEV. However, the flaw is unauthenticated, network reachable, and critical, so vulnerable exposed systems present a high business risk.

Researcher notes

Evidence is limited to CVE metadata and Turkish government advisory references. No endpoint, proof-of-concept, affected component, or exploit-in-the-wild detail is provided in the source bundle. Validate only through inventory, version checks, and vendor guidance.

Mitigation direction

  • Upgrade Kayrasoft to version 2 or later.
  • Check Kayrasoft or government advisory guidance for any additional required actions.
  • Prioritize internet-facing Kayrasoft systems for remediation.
  • If upgrade is delayed, reduce external exposure where operationally feasible.

Validation and detection

  • Inventory all Kayrasoft deployments and owners.
  • Verify each deployment is version 2 or later.
  • Confirm whether any Kayrasoft instance is internet reachable.
  • Review application and database logs for unusual unauthenticated errors or data access.
  • Track remediation evidence in vulnerability management records.
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 · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. 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

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration 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-2022-2177 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
Critical
CVSS
9.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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
2ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total

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
9.4CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L3.95.5TR-CERT

Vulnerability scoring details

Base CVSS 3.1 score

9.4Critical
CVSS 3.1 vector shape for CVE-2022-2177Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
KayrasoftKayrasoftunspecifiedunaffected
Weakness

CWE details

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

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.