# CVE-2018-25127: SOCA Access Control System 180612 Cross-Site Request Forgery via Admin Interface

> Attackers can trick logged-in administrators into creating new admin accounts via forged requests, leading to unauthorized privilege escalation.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Dec 2025
- **Updated:** 24 Dec 2025
- **Also known as:** GHSA-m662-6p96-4253

## What is CVE-2018-25127?

CVE-2018-25127 is a medium-severity vulnerability in SOCA Access Control System, published on 24 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

SOCA Access Control System 180612 contains a cross-site request forgery vulnerability that allows attackers to perform administrative actions without proper request validation. Attackers can craft malicious web pages that submit forged requests to create admin accounts by tricking logged-in users into visiting a malicious site.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2018-25127 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-25127 is a medium-severity vulnerability in SOCA Access Control System, published on 24 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25127 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-25127/ (Markdown: https://insights.sbomify.com/CVE-2018-25127/index.md)
```

## Sources

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

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