# CVE-2018-25128: SOCA Access Control System 180612 SQL Injection and Authentication Bypass

> Attackers can exploit SQL injection in SOCA Access Control System to bypass authentication, retrieve password hashes, and gain administrative privileges.

- **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:** 24 Dec 2025
- **Updated:** 24 Dec 2025
- **Also known as:** GHSA-754f-6hrq-f5qh

## What is CVE-2018-25128?

CVE-2018-25128 is a critical SQL injection vulnerability in SOCA Access Control System, published on 24 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SOCA Access Control System 180612 contains multiple SQL injection vulnerabilities that allow attackers to manipulate database queries through unvalidated POST parameters. Attackers can bypass authentication, retrieve password hashes, and gain administrative access with full system privileges by exploiting injection flaws in Login.php and Card_Edit_GetJson.php.

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

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


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

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

## Is CVE-2018-25128 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-25128 is a critical SQL injection vulnerability in SOCA Access Control System, published on 24 Dec 2025. 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-25128 exists.

Affected product: SOCA Access Control System. 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-25128/ (Markdown: https://insights.sbomify.com/CVE-2018-25128/index.md)
```

## Sources

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

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