LiveActive security incident?Get immediate response
CVE Record

CVE-2023-35072: SQLi in Coyav Travels Proagent

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Coyav Travel Proagent allows SQL Injection. This issue affects Proagent: before 20230904 .

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2023-35072 is a critical SQL injection vulnerability in Coyav Travel Proagent versions before 20230904. An unauthenticated remote attacker could potentially read, change, or disrupt database-backed application data. Public sources do not indicate active exploitation.

Executive priority

Treat as urgent where Proagent is used, especially if internet-facing. The vulnerability has maximum practical business impact because it may affect sensitive travel or customer data and system availability. Prioritize inventory, update confirmation, and exposure reduction.

Technical view

The CVE describes CWE-89 improper neutralization of SQL special elements in Coyav Travel Proagent before 20230904. CVSS 3.1 is 9.8: network-accessible, low complexity, no privileges, no user interaction, with high confidentiality, integrity, and availability impact.

Likely exposure

Organizations running internet-accessible Coyav Travel Proagent versions before 20230904 have the highest exposure. Internal-only deployments still carry risk if reachable by untrusted users or compromised hosts. The source bundle does not identify specific vulnerable endpoints or deployment prevalence.

Exploitation context

The CVSS vector indicates exploitation could be remote and unauthenticated. However, the provided sources do not include exploit details, proof-of-concept status, or evidence of active exploitation. CISA KEV status is false in the source bundle.

Researcher notes

Public detail is limited. The CVE record and advisories identify SQL injection and affected versions before 20230904, but do not provide vulnerable parameters, exploitability evidence, or detailed fix notes. One referenced USOM link is marked broken in the bundle; use the current siberguvenlik.gov.tr advisory where accessible.

Mitigation direction

  • Identify all Coyav Travel Proagent deployments and owners.
  • Upgrade Proagent to 20230904 or later if available from the vendor.
  • If upgrade is not immediately possible, follow Coyav or government advisory guidance.
  • Restrict network access to Proagent until remediation is confirmed.
  • Increase monitoring for suspicious database and application activity.

Validation and detection

  • Confirm each Proagent instance version or build date.
  • Verify no instance is running a version before 20230904.
  • Check whether internet-facing exposure exists for any Proagent deployment.
  • Review application and database logs for unusual errors or access patterns.
  • Document remediation status and compensating controls for each instance.
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-35072 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
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.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-35072Attack 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. 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
Coyav TravelProagent0unaffected
Weakness

CWE details

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