# CVE-2018-25129: SOCA Access Control System 180612 Information Disclosure via Multiple Endpoints

> Attackers can retrieve sensitive user credentials and PINs via unprotected endpoints in the SOCA Access Control System.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Dec 2025
- **Updated:** 24 Dec 2025
- **Also known as:** GHSA-wcqx-pwqh-x4mj

## What is CVE-2018-25129?

CVE-2018-25129 is a high-severity vulnerability in SOCA Access Control System, published on 24 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SOCA Access Control System 180612 contains multiple insecure direct object reference vulnerabilities that allow attackers to access sensitive user credentials. Attackers can retrieve authenticated and unauthenticated user password hashes and pins through unprotected endpoints like Get_Permissions_From_DB.php and Ac10_ReadSortCard.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2018-25129 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-25129 is a high-severity vulnerability in SOCA Access Control System, published on 24 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25129 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-25129/ (Markdown: https://insights.sbomify.com/CVE-2018-25129/index.md)
```

## Sources

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

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