# CVE-2025-67013: Cross-site request forgery in n/a

> Attackers can force authenticated users to perform unwanted actions on the DEXTRA Series web interface due to missing CSRF protections.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A: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 Dec 2025
- **Updated:** 26 Dec 2025
- **Also known as:** GHSA-4jf5-rmwc-7vww

## What is CVE-2025-67013?

CVE-2025-67013 is a medium-severity vulnerability in n/a, published on 26 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The web management interface in ETL Systems Ltd DEXTRA Series ' Digital L-Band Distribution System v1.8 does not implement Cross-Site Request Forgery (CSRF) protection mechanisms (no tokens, no Origin/Referer validation) on critical configuration endpoints.

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

## Which versions are affected by CVE-2025-67013?

It affects 27 products.


Products: Etlsystems C0401d1uia-22476 Firmware, Etlsystems C0401d1ula-22419 Firmware, Etlsystems C0401d1ula-22456 Firmware, Etlsystems C0401s1ula-22418 Firmware, Etlsystems C0401s1ula-22455 Firmware, Etlsystems C0801d1ula-22421 Firmware, Etlsystems C0801d1ula-22458 Firmware, Etlsystems C0801s1ula-22420 Firmware, Etlsystems C0801s1ula-22457 Firmware, Etlsystems C1601s1uia-22479 Firmware, Etlsystems C1601s1ula-22422 Firmware, Etlsystems C1601s1ula-22459 Firmware, Etlsystems D0104d1ula-22411 Firmware, Etlsystems D0104d1ula-22451 Firmware, Etlsystems D0104s1ula-22410 Firmware, Etlsystems D0104s1ula-22450 Firmware, Etlsystems D0108d1uia-22473 Firmware, Etlsystems D0108d1ula-22413 Firmware, Etlsystems D0108d1ula-22453 Firmware, Etlsystems D0108s1ula-22412 Firmware and 7 more.

## How do I fix CVE-2025-67013?

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

## Is CVE-2025-67013 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-67013 and fix it if it is affected.

What it is: CVE-2025-67013 is a medium-severity vulnerability in n/a, published on 26 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-2025-67013 exists.

Affected product: n/a. 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-2025-67013/ (Markdown: https://insights.sbomify.com/CVE-2025-67013/index.md)
```

## Sources

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

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