Skip to main content
VulnerabilityPublished

CVE-2025-68421: Comarch ERP Optima · Use of Hard-coded Credentials

Affects Comarch ERP OptimaSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 2026.4 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.4
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade Comarch ERP Optima to 2026.4.

Affected software

ProductAffectedFixed in
ComarchERP OptimaAffected
  • <2026.4
Fixed in
  • 2026.4

AI-suggested

Upgrade Comarch ERP Optima to version 2026.4 or later, where this vulnerability has been fixed. Since no other remediation or temporary fix is indicated, applying the official update is the recommended action. Patch status is not explicitly confirmed beyond the version fix note, so verify with the vendor advisory for the latest remediation guidance.

Description

Comarch ERP Optima client makes use of a hard-coded password for a database user. These credentials cannot be changed. It is possible for a remote attacker to gain an access to the database with elevated privileges including executing system commands on a server. This issue has been fixed in version 2026.4

References

Community reviews

Loading reviews…