# CVE-2018-25272: ELBA5 5.8.0 Remote Code Execution via Database Access

> Attackers can use default database credentials to decrypt passwords and execute arbitrary commands with SYSTEM privileges on ELBA5 servers.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Apr 2026
- **Updated:** 22 Apr 2026
- **Also known as:** GHSA-7xhq-2xxj-qpp5

## What is CVE-2018-25272?

CVE-2018-25272 is a critical vulnerability in ELBA5, published on 22 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ELBA5 5.8.0 contains a remote code execution vulnerability that allows attackers to obtain database credentials and execute arbitrary commands with SYSTEM level permissions. Attackers can connect to the database using default connector credentials, decrypt the DBA password, and execute commands via the xp_cmdshell stored procedure or add backdoor users to the BEDIENER table.

Weakness: CWE-326 (Inadequate Encryption Strength)

## Which versions are affected by CVE-2018-25272?


## How do I fix CVE-2018-25272?

No fix has been published for CVE-2018-25272 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-25272 being exploited?

There is no known exploitation of CVE-2018-25272 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25272 and fix it if it is affected.

What it is: CVE-2018-25272 is a critical vulnerability in ELBA5, published on 22 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-25272 in the wild and no public exploit code.

Affected product: ELBA5. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-25272/ (Markdown: https://insights.sbomify.com/CVE-2018-25272/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-25272
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-25272
- OSV: https://osv.dev/vulnerability/CVE-2018-25272

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-25272/
Summaries are generated and may contain mistakes; the official description above is the record.