dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-1198

HIGH · 8.6 CVSS v4.0 Published 2026-02-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
92/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
SIMPLE.ERP is vulnerable to the SQL Injection in search functionality in "Obroty na kontach" window. Lack of input validation allows an authenticated attacker to prepare a malicious query to the database that will be executed. This issue was fixed in [email protected]_u06.

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 confidence

SIMPLE.ERP contains a SQL injection vulnerability in the search functionality within the 'Obroty na kontach' window. Due to insufficient input validation, an authenticated attacker can inject malicious SQL statements through search parameters, potentially allowing unauthorized database access, data exfiltration, or data manipulation.

MitigationApply the vendor-supplied patch by upgrading to version [email protected]_u06, which implements proper input validation to sanitize SQL queries. Prioritize this upgrade given the HIGH CVSS score and the availability of authentication-protected exploit paths.

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
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm SIMPLE.ERP installation
    Locate the SIMPLE.ERP application on the system. Check for installation directory, desktop shortcut, or program entry in Add/Remove Programs.
    Affected if SIMPLE.ERP is present on the system
  2. Identify installed SIMPLE.ERP version
    Access the application's About or System Information section, typically found in Help menu, or check version info in the installation directory.
    Affected if Version is lower than [email protected]_u06 (the fixed release)
  3. Verify 'Obroty na kontach' module accessibility
    Log into SIMPLE.ERP and navigate to or attempt to access the 'Obroty na kontach' window within the application.
    Affected if The 'Obroty na kontach' window is accessible with valid credentials
  4. Confirm authentication is active
    Verify that the application requires user authentication to access the 'Obroty na kontach' functionality. SQL injection requires valid credentials to reach the vulnerable search.
    Affected if User authentication is configured and functional, but application version is before [email protected]_u06

If SIMPLE.ERP is installed with a version lower than [email protected]_u06 and the 'Obroty na kontach' window is accessible to authenticated users, the environment is affected by this SQL injection vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied patch by upgrading to version [email protected]_u06, which implements proper input validation to sanitize SQL queries. Prioritize this upgrade given the HIGH CVSS score and the availability of authentication-protected exploit paths.

Recommended fix Moderate confidence

[email protected]_u06

  1. 1. Identify the current version of SIMPLE.ERP installed in your environment
  2. 2. If the current version is earlier than [email protected]_u06, plan an upgrade to version [email protected]_u06 or later
  3. 3. Before upgrading, perform a full backup of the database and application files
  4. 4. Test the upgrade in a non-production environment to verify compatibility
  5. 5. Apply the upgrade following SIMPLE.ERP standard upgrade procedures
  6. 6. After upgrade, verify that the SQL Injection vulnerability in the 'Obroty na kontach' search functionality is resolved
  7. 7. Confirm input validation is properly functioning in the search fields

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1198 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1198 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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