# CVE-2019-25675: eDirectory All Versions SQL Injection Authentication Bypass

> Unauthenticated attackers can bypass administrator authentication via SQL injection and read arbitrary files from the server.

- **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:** 5 Apr 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-j8vm-fq36-j7vq

## What is CVE-2019-25675?

CVE-2019-25675 is a high-severity SQL injection vulnerability in eDirectory, published on 5 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

eDirectory contains multiple SQL injection vulnerabilities that allow unauthenticated attackers to bypass administrator authentication and disclose sensitive files by injecting SQL code into parameters. Attackers can exploit the key parameter in the login endpoint with union-based SQL injection to authenticate as administrator, then leverage authenticated file disclosure vulnerabilities in language_file.php to read arbitrary PHP files from the server.

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

## Which versions are affected by CVE-2019-25675?

It affects 1 product.


Products: Arcasolutions Edirectory.

## How do I fix CVE-2019-25675?

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

## Is CVE-2019-25675 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25675 and fix it if it is affected.

What it is: CVE-2019-25675 is a high-severity SQL injection vulnerability in eDirectory, published on 5 Apr 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-2019-25675 exists.

Affected product: eDirectory. 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-2019-25675/ (Markdown: https://insights.sbomify.com/CVE-2019-25675/index.md)
```

## Sources

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

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