CVE-2025-4738
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Yirmibes Software MY ERP allows SQL Injection. This issue affects MY ERP: before 1.170.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA critical SQL injection vulnerability exists in Yirmibes Software MY ERP due to improper neutralization of special elements in SQL commands. Attackers can inject malicious SQL queries through user-supplied input to manipulate database operations, potentially gaining unauthorized access to sensitive data or compromising the entire system. This affects all versions before 1.170.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed MY ERP versionAccess the application's About page, check the version displayed in the software interface, or query the version from the system's installed packages/database if administrative access is availableAffected if The version is lower than 1.170 (for example, 1.160, 1.150, etc.)
-
Confirm the application is deployed and accessibleVerify that the Yirmibes MY ERP web interface or API is running and reachable over the networkAffected if The application is live and processing user requests, making it potentially exploitable
-
Locate user-supplied input fieldsReview application forms, search fields, login parameters, URL query strings, and API endpoints that accept user input and interact with the databaseAffected if Input fields that are not properly sanitized before being used in SQL queries are present and accessible to users
Your environment is affected if MY ERP version is below 1.170 and the application is deployed with user-accessible input fields that interact with the database.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to MY ERP version 1.170 or later to obtain the security patch. Until then, restrict network access to the application and implement web application firewall rules to detect and block SQL injection attempts.
1.170
- Identify all deployments of Yirmibes Software MY ERP in your environment
- Verify the currently installed version of MY ERP
- If the installed version is before 1.170, obtain the updated version 1.170 or later from the vendor
- Follow the vendor's standard upgrade procedure to apply the update
- After upgrading, verify the fix by testing the application functionality
- Consider performing security testing to confirm the SQL injection vulnerability is no longer present
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-4738 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-4738 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data