Security readout for executives and security teams
Plain-English summary
Yirmibes Software MY ERP versions before 1.170 have a critical SQL injection vulnerability. If an organization runs an affected MY ERP instance, an attacker may be able to manipulate backend database queries, creating risk to sensitive business data, records integrity, and service availability.
Executive priority
Treat this as urgent for any organization using MY ERP. Confirm exposure quickly, prioritize upgrade or access restriction, and assign ownership because the potential business impact includes data compromise, record tampering, and service disruption.
Technical view
CVE-2025-4738 is a CWE-89 SQL injection in Yirmibes Software MY ERP before 1.170. The CVSS 3.1 score is 9.8 with network attack vector, low complexity, no user interaction, and high confidentiality, integrity, and availability impact. The source bundle does not provide endpoint-level details.
Likely exposure
Exposure is likely limited to organizations running Yirmibes Software MY ERP earlier than 1.170. Risk is highest where MY ERP is reachable from untrusted networks. The source bundle provides no CPEs, deployment guidance, or asset-discovery fingerprints.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and the cited sources do not state active exploitation. The CVSS vector indicates the issue may be remotely reachable with low attack complexity, but exploit availability is not established by the provided evidence.
Researcher notes
Evidence is limited. The title says authenticated SQL injection, while the CVSS vector says privileges are not required. The affected-version metadata lists version "0" but the description says before 1.170. Validate version interpretation against CVE and government advisories before final exposure conclusions.
Mitigation direction
- Identify all Yirmibes Software MY ERP deployments and record their exact versions.
- Upgrade MY ERP to 1.170 or later if confirmed by vendor guidance.
- If upgrade is delayed, restrict MY ERP access to trusted networks and authenticated users.
- Review vendor and Turkish government advisories for any updated remediation instructions.
- Increase monitoring around MY ERP database errors and suspicious request patterns.
Validation and detection
- Confirm whether any MY ERP instance is running a version before 1.170.
- Check internet exposure and access controls for all MY ERP interfaces.
- Review logs for unusual SQL errors, abnormal queries, or unexpected data access.
- Verify remediation against vendor or government advisory language.
- Retest only with authorized, non-destructive validation methods.
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-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 lookupDatabase 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 lookupCVE-2025-4738 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
- 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
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:H/I:H/A:H3.95.9TR-CERTVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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-0132CVE reference, TR-CERT · government-resource, broken-link
- https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-25-0132CVE 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 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.