LiveActive security incident?Get immediate response
CVE Record

CVE-2023-1267: SQLi in Ulkem Company's PtteM Kart

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Ulkem Company PtteM Kart. This issue affects PtteM Kart: before 2.1.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2023-1267 is a critical SQL injection flaw in Ulkem Company PtteM Kart before version 2.1. A remote, unauthenticated attacker could potentially affect confidentiality, integrity, and availability. Public sources do not show active exploitation in KEV, but the CVSS profile makes exposed deployments urgent to identify.

Executive priority

Treat this as urgent for any confirmed PtteM Kart deployment. The issue has critical impact and remote unauthenticated reachability. Priority is lower only if the organization can prove it does not run the product or has no affected versions exposed.

Technical view

The vulnerability is CWE-89 SQL injection caused by improper neutralization of SQL command elements. The CVSS 3.1 score is 9.8 with network attack vector, low complexity, no privileges, and no user interaction. The source names PtteM Kart versions before 2.1 as affected, though structured affected-version metadata is sparse.

Likely exposure

Exposure is most relevant for organizations running Ulkem Company PtteM Kart before 2.1, especially if reachable over the internet. CPE data is absent, so automated scanners may miss it. Confirm product ownership and version through asset inventory, vendor records, and application teams.

Exploitation context

The provided bundle marks KEV as false and includes no cited evidence of active exploitation. The CVSS vector indicates the bug is remotely reachable without authentication or user interaction, which raises risk even without confirmed exploitation.

Researcher notes

Evidence is limited to the CVE record and Turkish government references. The source states before 2.1 is affected, but the structured affected data lists version metadata sparsely and no CPEs. Do not infer exploit availability or detailed fixes beyond vendor or advisory confirmation.

Mitigation direction

  • Identify any Ulkem Company PtteM Kart deployments and owners.
  • Move deployments off versions before 2.1 where vendor guidance confirms availability.
  • Review the Turkish government advisory and vendor guidance for exact remediation.
  • Restrict external access until remediation is confirmed.
  • Increase monitoring for database errors and suspicious application requests.

Validation and detection

  • Confirm deployed PtteM Kart versions against the before-2.1 affected range.
  • Check whether the application is internet-facing or reachable from untrusted networks.
  • Review logs for unusual SQL errors, authentication anomalies, or unexpected data access.
  • Verify remediation through version evidence, not only package names.
  • Document any systems where version cannot be determined.
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-2023-1267 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.8 (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:H

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
9Timeline events
2ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical 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.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9TR-CERT

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2023-1267Attack 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:H

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. Source timelineTR-CERT

    Vulnerability detected

  2. Source timelineTR-CERT

    Vendor informed about vulnerability

  3. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  4. Source timelineTR-CERT

    Vulnerability fixed by the vendor

  5. Source timelineTR-CERT

    Vulnerability fix confirmed by the TR-CERT

  6. Source timelineTR-CERT

    TR-23-0133 Security Bulletin published by the TR-CERT

  7. Source timelineTR-CERT

    CVE Published

  8. CVE publishedCVE Program

    The CVE record was published.

  9. 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
Ulkem CompanyPtteM Kart0unaffected
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.