# CVE-2018-25209: OpenBiz Cubi Lite 3.0.8 SQL Injection via username Parameter

> Unauthenticated attackers can exploit SQL injection in the login form to extract database information or bypass authentication in OpenBiz Cubi Lite.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/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:** 26 Mar 2026
- **Updated:** 26 Mar 2026
- **Also known as:** GHSA-85vx-gmj9-6wff

## What is CVE-2018-25209?

CVE-2018-25209 is a high-severity SQL injection vulnerability in Sourceforge OpenBiz Cubi Lite, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenBiz Cubi Lite 3.0.8 contains a SQL injection vulnerability in the login form that allows unauthenticated attackers to manipulate database queries through the username parameter. Attackers can submit POST requests to /bin/controller.php with malicious SQL code in the username field to extract sensitive database information or bypass authentication.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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


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

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

## Is CVE-2018-25209 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25209 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2018-25209 is a high-severity SQL injection vulnerability in Sourceforge OpenBiz Cubi Lite, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25209 exists.

Affected product: Sourceforge OpenBiz Cubi Lite. 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-25209/ (Markdown: https://insights.sbomify.com/CVE-2018-25209/index.md)
```

## Sources

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

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